GNOME.org
 

[gnome-db] More Questions? THXS




Assasination of PIM Fortuyn in the Netherlands



From: gnome-db-list-request gnome org
Reply-To: gnome-db-list gnome org
To: gnome-db-list gnome org
Subject: gnome-db-list Digest, Vol 11, Issue 15
Date: Tue, 22 Mar 2005 12:00:43 -0500 (EST)

Send gnome-db-list mailing list submissions to
	gnome-db-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.gnome.org/mailman/listinfo/gnome-db-list
or, via email, send a message with subject or body 'help' to
	gnome-db-list-request gnome org

You can reach the person managing the list at
	gnome-db-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gnome-db-list digest..."


Today's Topics:

   1. Re: API change for GdaConnection (Rodrigo Moya)
   2. Re: API change for GdaConnection (Vivien Malerba)
   3. Re: API change for GdaConnection (Vivien Malerba)
   4. Re: API change for GdaConnection (Rodrigo Moya)


----------------------------------------------------------------------

Message: 1
Date: Tue, 22 Mar 2005 11:55:00 +0100
From: Rodrigo Moya <rodrigo gnome-db org>
Subject: Re: [gnome-db] API change for GdaConnection
To: Vivien Malerba <vmalerba gmail com>
Cc: gnome-db list <gnome-db-list gnome org>
Message-ID: <1111488900 5114 31 camel cerler home>
Content-Type: text/plain

On Mon, 2005-03-21 at 15:03 +0100, Vivien Malerba wrote:
> Hi!
>
> I've looked into all the providers and realized that the
> "GdaParameterList *params" argument of the
> gda_connection_execute_command() method is never used, so I propose to
> remove it, as there is also no documentation for its usage (which is
> normal considered it's never used).
>
if we remove it, we need to think about a way for using parametrised
commands. That's the only purpose of the GdaParameterList. I guess we
could just do it at the GdaCommand level.

> This is a starting point in improving the libgda API useability.
>
> I'm also planning to add asychronous query execution to be able to
> have more responsive GUI applications. I'll submit a proposal API
> before any actual implementation.
>
that is a very good idea.
--
Rodrigo Moya <rodrigo gnome-db org>



------------------------------

Message: 2
Date: Tue, 22 Mar 2005 14:05:27 +0100
From: Vivien Malerba <vmalerba gmail com>
Subject: Re: [gnome-db] API change for GdaConnection
To: Murray Cumming <murrayc murrayc com>
Cc: Rodrigo Moya <rodrigo gnome-db org>,	gnome-db-list
	<gnome-db-list gnome org>
Message-ID: <bd20ce3f05032205053e1bd2f7 mail gmail com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, 22 Mar 2005 13:04:40 +0100, Murray Cumming <murrayc murrayc com> wrote: 
> On Tue, 2005-03-22 at 11:55 +0100, Rodrigo Moya wrote:
> > On Mon, 2005-03-21 at 15:03 +0100, Vivien Malerba wrote:
> > > Hi!
> > >
> > > I've looked into all the providers and realized that the
> > > "GdaParameterList *params" argument of the
> > > gda_connection_execute_command() method is never used, so I propose to 
> > > remove it, as there is also no documentation for its usage (which is
> > > normal considered it's never used).
>
> It is used to get schema information. For instance, when using
> GDA_CONNECTION_SCHEMA_FIELDS, the first parameter should be the table
> name. That's documented a bit.
That's the gda_connection_get_schema() method, which I do not intend to change. 

>
> I agree that it should be part of the command, instead a function
> parameter.

Yes, I think it should be part of the GdaCommand object (which BTW is
not an object).

Vivien


------------------------------

Message: 3
Date: Tue, 22 Mar 2005 14:15:40 +0100
From: Vivien Malerba <vmalerba gmail com>
Subject: Re: [gnome-db] API change for GdaConnection
To: Rodrigo Moya <rodrigo gnome-db org>
Cc: gnome-db list <gnome-db-list gnome org>
Message-ID: <bd20ce3f0503220515609082ba mail gmail com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, 22 Mar 2005 11:55:00 +0100, Rodrigo Moya <rodrigo gnome-db org> wrote: 
> On Mon, 2005-03-21 at 15:03 +0100, Vivien Malerba wrote:
> > Hi!
> >
> > I've looked into all the providers and realized that the
> > "GdaParameterList *params" argument of the
> > gda_connection_execute_command() method is never used, so I propose to
> > remove it, as there is also no documentation for its usage (which is
> > normal considered it's never used).
> >
> if we remove it, we need to think about a way for using parametrised
> commands. That's the only purpose of the GdaParameterList. I guess we
> could just do it at the GdaCommand level.

Yes. Also I noticed that parametrised commands are not implemented
(there is a /*FIXME*/ in the gda_sql_replace_placeholders() function,
which BTW is never used in libgda), which means this functionnality is
not used at all.

There are two possibilities about that then:
1- implemente that function, and make sure it's used everywhere where
appropriate
2- Remove that functionnality from libgda and use the same
functionnality provided by libgnomedb (which works).

I'd vote for the 2nd choice.

>
> > This is a starting point in improving the libgda API useability.
> >
> > I'm also planning to add asychronous query execution to be able to
> > have more responsive GUI applications. I'll submit a proposal API
> > before any actual implementation.
> >
> that is a very good idea.

Yes, I think it's really something missing. The problem I have at the
moment is how to cope with transactions correctly, and I have no
solution at the moment.

About transactions, I think the gda_client_*_transaction() methods are
dangerous to use as it does not guarantee anything even though it lets
the user suppose that he will benefit from a global transaction on all
the connections the client has. It also does not grarantee that when
gda_client_begin_transaction() is successfully called, the contents of
the database is strictly the same for all the connections (as it's not
an atomic operation from the database point of view). So I propose to
remove the  gda_client_*_transaction() methods altogether. What do you
think?

That's quite a lot of changes, but I think they are necessary to have
a better API.

Cheers,

Vivien


------------------------------

Message: 4
Date: Tue, 22 Mar 2005 14:12:19 +0100
From: Rodrigo Moya <rodrigo gnome-db org>
Subject: Re: [gnome-db] API change for GdaConnection
To: Vivien Malerba <vmalerba gmail com>
Cc: gnome-db-list <gnome-db-list gnome org>,	Murray Cumming
	<murrayc murrayc com>
Message-ID: <1111497139 32092 3 camel cerler home>
Content-Type: text/plain

On Tue, 2005-03-22 at 14:05 +0100, Vivien Malerba wrote:
> On Tue, 22 Mar 2005 13:04:40 +0100, Murray Cumming <murrayc murrayc com> wrote: 
> > On Tue, 2005-03-22 at 11:55 +0100, Rodrigo Moya wrote:
> > > On Mon, 2005-03-21 at 15:03 +0100, Vivien Malerba wrote:
> > > > Hi!
> > > >
> > > > I've looked into all the providers and realized that the
> > > > "GdaParameterList *params" argument of the
> > > > gda_connection_execute_command() method is never used, so I propose to > > > > remove it, as there is also no documentation for its usage (which is 
> > > > normal considered it's never used).
> >
> > It is used to get schema information. For instance, when using
> > GDA_CONNECTION_SCHEMA_FIELDS, the first parameter should be the table
> > name. That's documented a bit.
>
> That's the gda_connection_get_schema() method, which I do not intend to change. 
>
> >
> > I agree that it should be part of the command, instead a function
> > parameter.
>
> Yes, I think it should be part of the GdaCommand object (which BTW is
> not an object).
>
right, I guess it makes sense to make it a GObject also.
--
Rodrigo Moya <rodrigo gnome-db org>



------------------------------

_______________________________________________
gnome-db-list mailing list
gnome-db-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-db-list


End of gnome-db-list Digest, Vol 11, Issue 15
*********************************************


_________________________________________________________________
Find love today with ninemsn personals. Click here: http://ninemsn.match.com?referrer=hotmailtagline
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]