Re: possible?

[Rodrigo Moya Piernavieja <rmoya tsai es>]

>
> >
> > I've moved programs (albeit VB) from Access to MSSQL, and boy was that fun.
> > However, I still had to re-write code, including my SQL statements. Does
> > GnomeDB hide that from the program? Will I have to write a wrapper anyways
> > for every DB engine GnomeDB supports anyways to take care of the quirks
> > (like no caching, or weird datatypes), or do I get it just like it's in the
> > database. I can see the case for either, however, for my program, I want
> > all to be the same. =)
> >
>
> gnome-db is implemented as a set of DB providers (CORBA servers) which map the
> specific database API to the gnome-db model, and a client library which acts
> as a thin wrapper around all the CORBA stuff, so you use this client library
> to access the different providers regardless of the underlying API. So, there
> is no need to write specific code per-database, you just use the client lib.
> Caching is done in the client library, and each provider is responsible for
> mapping their specific data types to the gnome-db datatypes, which are a set
> of types that cover almost every possible data type in a database.
>

Well, reading through this mail, I've remembered a problem I found when
implementing the new XML stuff, which is: how can I issue standard SQL commands
(such as "select * from table" or "update ....") in a way understable by all the
providers? because there are placesin the GDA libs
(gda_xml_table_new_from_gda_recordset and this GnomeDbReport) where you must
issue these commands. The first thing that comes to my mind is to use standard
SQL (SQL92 or something like that?), but, what will happen with no-DBMS providers
(LDAP, XML, ...)? and maybe standard SQL means less flexibility for some
providers that do have extra stuff.