You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm always frustrated when the current DSN (Data Source Name) for PostgreSQL database as it does not support specifying a schema for databases that require schema selection. This results in needing to manually set the schema after establishing a connection or handling it separately in the code.
Describe the solution you'd like
I would like to have the ability to specify a schema directly within the DSN so that when a connection is established, the appropriate schema is selected automatically.
Describe alternatives you've considered
An alternative solution would be to execute a query to set the schema immediately after the connection is established, but this adds complexity and overhead to the connection process.
Additional context
This feature would streamline connections for databases with multiple schemas and reduce manual configuration.
The text was updated successfully, but these errors were encountered:
1saifj
changed the title
support selecting a db schema if found
Support selecting a DB schema if found
Oct 17, 2024
1saifj
changed the title
Support selecting a DB schema if found
Support selecting a PostgreSQL DB schema if found
Oct 17, 2024
On the generate code page, the next Sponge release adds the specified schema parameters, such as root:123456@(192.168.3.37:5432)/account?search_path=job
My plan is to add a toggle switch to enable/disable scanning multiple schemas, and if it's enabled, a schema prefix should be added when generating GORM code.
Is your feature request related to a problem? Please describe.
I'm always frustrated when the current DSN (Data Source Name) for PostgreSQL database as it does not support specifying a schema for databases that require schema selection. This results in needing to manually set the schema after establishing a connection or handling it separately in the code.
Describe the solution you'd like
I would like to have the ability to specify a schema directly within the DSN so that when a connection is established, the appropriate schema is selected automatically.
Describe alternatives you've considered
An alternative solution would be to execute a query to set the schema immediately after the connection is established, but this adds complexity and overhead to the connection process.
Additional context
This feature would streamline connections for databases with multiple schemas and reduce manual configuration.
The text was updated successfully, but these errors were encountered: