Re: [gnome-db] Updates to Postgres provider

[Vivien MALERBA <malerba gnome-db org>]

Le jeu 22/08/2002 à 00:24, Rodrigo Moya a écrit :
> On Wed, 2002-08-21 at 17:19, Vivien MALERBA wrote:
> > Hi!
> >
> > I've been working on the updates to the postgres provider regarding the
> > extended schemas (Bug 84357). I've also looked at what the MySQL
> > provider does and the docs. Here what I have modified/implemented so
> > far:
> >
> > * GDA_CONNECTION_SCHEMA_TYPES:
> > No param taken into account (that should be added), the returned set
> > holds the following columns:
> >      - unique ID for the data type (actually a Postgres OID)
> >      - type name
> >      - owner name
> >      - type description
> >
> shouldn't here the type name be the first field, as we do for the
> currently implemented schemas. I think it is better to have the name as
> the first field, since it is the field which will be used the most in
> applications.

Oops, sorry I made a mistake. I just looked at the SQL query sent to the
postgres provider which makes the OID appear, but when the GdaDataModel
is made, the oid is lost (the data type name must be unique, no need for
another id column). The real returned columns are:
     - type name
     - owner
     - comments
     - corresponding Gda type

>
> > ...
>
> The same comment for the other schemas having the ID as the first field.
> The rest looks perfect to me.

Ok, Im going to swap the Id column and the name column for the
GDA_CONNECTION_SCHEMA_PROCEDURES and GDA_CONNECTION_SCHEMA_AGGREGATES.

>
> >
> >
> > This differs slightly from what the libgda doc says, but I need the
> > extra infos for Mergeant. How about updating the sets returned by the
> > other providers to be the same as for Postgres?
> >
> I'll do it in mysql. But, anyway, it would be nice if you could upgrade
> the documentation on this (libgda/doc/C/libgda-docs.sgml), so that it
> gets written for people working on providers, and to avoid confusion.

Ok. I'm going to update the libgda's documentation.

Cheers,

Vivien