lazysql

Lazysql uses a Non-blocking Loading pattern for database operations. When a query is in-flight, the UI remains interactive rather than showing a blocking modal or overlay.

Key behaviors:

• Loading Indicator: A thin text indicator appearing on the table's pagination bar (e.g., "Loading...") shows progress without stealing focus or blocking input.
• Stale Data: Old table results remain visible during a reload to prevent a blank screen. Data is only cleared once the new results arrive successfully. (Exception: SQL editor queries clear immediately upon execution).
• Load Cancellation: If a new load is triggered while an operation is already in-flight, the previous operation is cancelled via context cancellation before the new one begins.

In the Lazysql terminal UI, use Foreign Key Jump to navigate from a selected cell in a source row to a referenced table view. This action automatically applies a prefilled filter to the target table based on the selected foreign key value.

Note: Do not use terms like "FK drilldown", "relation follow", or "link jump" when referring to this feature; the canonical term is Foreign Key Jump.

Use the Application methods to retrieve or persist database connections.

• Connections(): Returns a slice of models.Connection currently in the configuration.
• SaveConnections(connections []models.Connection): Persists a new slice of connections to the configuration.

The Application struct provides methods to access internal state:

• Context(): Returns the context.Context used by the application.
• Config(): Returns the *models.AppConfig object.
• Connections(): Returns the list of models.Connection objects.

The Stop() method initiates a graceful shutdown by:

1. Canceling the application's context.Context.
2. Waiting for all tasks registered via Register() to complete.
3. Stopping the underlying tview.Application.

To ensure the application does not exit before background tasks (like saving data or closing connections) are complete, use the Register() method.

Register() increments an internal wait group and returns a function. You must call this returned function (which is sync.WaitGroup.Done) when your task is finished. The Stop() method will block until all registered tasks have called their respective completion functions.

Lazysql uses a Command type (based on uint8) to represent all possible user actions and system operations. These commands are used to trigger view switches, movement, menu interactions, and database operations. When working with the internal command system, you can use these constants to dispatch actions.

// Example of the Command type definition
type Command uint8

const (
	Noop Command = iota
	SwitchToEditorView
	SwitchToConnectionsView
	// ... other commands
)

LazySQL is a command-line tool for interacting with databases. You can start it in 'picker mode' to select a connection from your configuration, or provide a specific database URL to connect directly.

Usage Patterns:

• Picker Mode: Run lazysql without arguments to see a list of configured connections.
• Direct Connection: Run lazysql [connection_url] to connect to a specific database immediately.

Note: Only a single connection URL is allowed as a command-line argument.