Now when storing settings has been standardasied we're in position to take more systematic approach to this problems.
I believe there should be dialog to enter global preferences, at the moment they are set implicitly based on last state. That's ok in some cases, but I belive that preferred SQL dialect and character set should be entered explicitly. We could then add new options freely.
Do we need separate preferences for database connection and database creation?
In SQL options dialog there should be set only 'SQL options' and possibly for _current_ connection. For example SQL dialect and character for current connection only. At the moment they are saved as global preferences only!
Character set usage at the moment very consusing, people reported it a lot of times. Too make things more clear more visual info should be provided on current connection, database properties and global settings.
Hope to hear from you.
Kris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now when storing settings has been standardasied we're in position to take more systematic approach to this problems.
I believe there should be dialog to enter global preferences, at the moment they are set implicitly based on last state. That's ok in some cases, but I belive that preferred SQL dialect and character set should be entered explicitly. We could then add new options freely.
Do we need separate preferences for database connection and database creation?
In SQL options dialog there should be set only 'SQL options' and possibly for _current_ connection. For example SQL dialect and character for current connection only. At the moment they are saved as global preferences only!
Character set usage at the moment very consusing, people reported it a lot of times. Too make things more clear more visual info should be provided on current connection, database properties and global settings.
Hope to hear from you.
Kris