[gnome-db] Re: SQL command history

[Vivien Malerba STNA 7FD M204 <vivien malerba aviation-civile gouv fr>]

Rodrigo Moya wrote:

> Right now, the SQL command history on the SQL page is not saved
between
> sessions, so you lose all of them as soon as you close Mergeant.
> 
> I wanted to change that, and came up to a doubt, which is where to
store
> them. That is, for the gnome-db front end, they were saved in GConf,
> with the rest of the configuration, but since in Mergeant we are using
a
> file, I wonder if that should be added to the file, so that if you
send
> the file to another person, he/she will get also the list of commands.
> 
> So, what do you think? Vivien, what would be needed to add that to the
> mergeant file format? Do I have to extend the DTD, right?


I have a short and a long answer, the long is better!

The short answer to this is yes, I also prefer to store the SQL query in
the opened file.

Here is the longer answer:
For now, it is possible to create queries in mergeant (thay appear in
the 'Queries' page); these queries can be of the following 'type': DATA
Selection, DATA insertion, DATA update, DATA Delete, UNION, INSERSECT,
etc of other sub queries, and SQL only query. 

I've concentrated my work only on the first type mentionned above. The
latest is also possible but it is very poor.

What I propose is the following:
-> we store the SQL queries history of the 'SQL console' somewhere in
the XML file (needs a modification of the DTD)
-> when the user clicks on the 'save to disk' icon (the one in the SQL
console), mergeant creates a new query which appears in the 'Queries'
tab with a type of 'SQL only', this means adding a dialog to ask for a
query's name (this needs no modification of the DTD). Maybe we nned to
change the icon to something more meaningfull.
-> we remove the 'open file' icon

How does it sound?

Vivien