Re: gEDA-user: database driven component chooser - part II

[Christoph Lechner <cl0023@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jonatan Åkerlind wrote:
> On sön, 2007-09-30 at 13:33 +0000, Levente wrote:
>> But in a nutshell, it looks up a component from a mySQL database, and
>> parse the result. The database is online, and so you can see what is
>> inside.
> 
> How hardcoded is it towards mySQL? After all postgresql is a good
> alternative often forgotten about.
Usually porting between MySQL and postgresql isn't that hard, given the
MySQL SQL queries follow the SQL standard. The problem is that MySQL
accepts some SQL queries that other DB packages like postgresql don't
accept! A quite popular mistake is not to list all fields you don't use
an aggregate function on in your GROUP BY clause. MySQL accepts this ...
while others don't.

CU
- - cl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHANdZWo2QgtqY4K8RAh+DAJsF/4eo8Cwt0oh+rcALaFHmN9GG8ACfR6iw
zgVxs6Wok0wrMQpY6MFPNpM=
=pLl8
-----END PGP SIGNATURE-----


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user