Re: [gnome-db] Re: gASQL status

[Rodrigo Moya <rodrigo gnome-db org>]

On Wed, 2002-05-22 at 14:36, Malerba_Vivien stna dgac fr wrote:
> > 
> > I am right now studying gASQL code to know how to replace all libgda
> > usage, so this shouldn't be difficult.
> 
> This should be fairly easy...
> 
oh, that's nice to hear, since the other day I was a bit worried that it
might be too much work.

> > 
> > > > 
> > > > > - insert the SQL command window
> > > > >
> > > > the widget is in libgnomedb, so I'll wait for you to come back home to
> > > > tell me where to insert it in the gASQL code.
> > > 
> > > This one's easy in 3/4 steps:
> > > - make or copy a nice icon
> > > - add it to the in the same way as the MainPageTable, MainPageSeq,
> > > MainPageQuery and MainPageEnv which are the 4 widgets which make the
> > > main area in the window. This is done in conf-manager.c, in
> > > build_main_window(), and a new callback function to be needs to be
> > > defined in interface_cb.[hc].
> > > - change the default window size so all the icons in the left bar can be
> > > displayed.
> > > - MAYBE: modify the gasql.dtd to be able to save the queries done in the
> > > SQL editor at the same time as all the rest.
> > > 
> > ok, I'll take this task for me, although we first need to port to the
> > new libgda API.
> 
> Right. I thought that maybe it was a better idea to open a new dialog
> window in which to display the SQL console, and so we can have more
> space in the dialog than in the gASQL's main window (this means adding a
> menu entry or a toolbar icon)?
> 
please add a bug to bugzilla about it, and, as soon as we finish the
porting, I'll do that task myself.

                                                                                                                                                                                                                                                                                                                                
> > 
> > > - we need to allow the application to know what options the provider
> > > accepts to adapt the GUI to what is available only
> > >
> > ok, that is perfectly doable. What are the options you're thinking
> > about?
> 
> Several options:
> - types of rights (read, insert, update, or read, write, etc);
> - if rights are managed at the level of a database, a table or some
> columns of a table, sequence, index, vues...
> - the kind of rights for a user (create DBs, create other users, change
> passwords of other users, etc).
> - maybe other ones.
> 
ok, please add all this to another bug, and I'll take care of it.

> 
> > > > I already added the create_database method on providers, so I'll just
> > > > add a drop_database method, ok?
> > > 
> > > Right.
> > > 
> > ok, I also take this task.
> > 
> 
> Ok.
> 
this is now done in CVS.

> > > 
> > > That's a nice idea and will simplify coding on the client side!
> > > Does it also work with tables' structures and other schemas? 
> > > 
> > we are starting the implementation in the different providers. The idea,
> > so far, is to have providers able to identify each row they get from the
> > database, and if so, have that data model be editable.
> > As a starting point, I think we'll just make it work with tables (that
> > is, a "SELECT * FROM table", not JOINs or other schemas). But as soon as
> > we've got the basic stuff, we can extend it as we like.
> > 
> > That's the best thing about the new libgda: it's so well designed that
> > it's easy to add new functionality :-)
> 
> That is a good idea. With the is_editable() method you mention next, we
> have the best of both worlds!
> 
:-)

cheers