Re: [vos-d] Re: Re: next priorities; mySQL

2006-04-10 Thread Reed Hedges
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Neil Mosafi wrote:
> Surely the best approach is trying to support as many different database
> servers as possible, rather than pushing a single one onto the VOS user?
> 
> To that extent, does anyone know of a flexible C++ data access library which
> can be configured to talk to many different databases?  I am talking not
> only MySql, Postgres etc but also commercial ones like Oracle and Microsoft
> SQL Server (or MS SQL Express, which is free)?

As long as it can handle very simple and very standard SQL queries, then
it ought to be really easy to add support for it to the sqlpersist
extension. Though if you get too many databases involved, sqlpersist
might need to be split into seperate extensions for each database with a
 common library for the abstract classes, or use plugins.

http://interreality.org/cgi-bin/moinwiki/moin.cgi/SqlPersistanceExtension


Reed


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEOvGYFK83gN8ItOQRArzUAKCFj94HfHQiODsUjqbnOcQwjLur7ACfaXVL
xaCqVCieQDf+HliWCoNh2Hk=
=RkEn
-END PGP SIGNATURE-

___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d


Re: [vos-d] Re: Re: next priorities; mySQL

2006-04-10 Thread Reed Hedges
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Fair enough criticism I guess; you're passionate about it though! The
mysql interface code (mysqldb.cc, mysqldb.hh) is about 65  lines, so go
for it if you want something better :)   The interface class to subclass
is in sqldb.hh.


(I'll also add it as a wishlist item on the Wiki.)

Reed


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEOvBrFK83gN8ItOQRAhjVAJ9SZl3k1RPJnyIT+BuQljVdH/eJJwCdEjd0
CwpocvS6vdZ7bJYoCjbFBSg=
=P3yH
-END PGP SIGNATURE-

___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d


Re: [vos-d] Re: Re: next priorities; mySQL

2006-04-10 Thread Neil Mosafi
Surely the best approach is trying to support as many different database servers as possible, rather than pushing a single one onto the VOS user?To that extent, does anyone know of a flexible C++ data access library which can be configured to talk to many different databases?  I am talking not only MySql, Postgres etc but also commercial ones like Oracle and Microsoft SQL Server (or MS SQL Express, which is free)?
On 10/04/06, Lalo Martins <[EMAIL PROTECTED]> wrote:
On Sun, 09 Apr 2006 18:55:29 -0400, Reed Hedges wrote:>> my personal goal for .24 would be refurbishing the sqlpersist machinery. I>> just don't trust mysql at all ;-)>> What do you mean, you don't trust it?
>> What about PostgreSQL then?I know MySQL is now a complete proper database system, with ACID and all.But up to just a few months ago, it was just a place to dump your datathat happened to (mostly) respond to SQL queries.  It gained so much
popularity because it was fast; but anyone who really caredabout this database stuff knew that it was faster because it wasincomplete.  Like, well, DOS is faster than WinXP.And even now, at least last time I looked, the "completeness"
(ACID compliance and whatever else) is optional... the defaultsetup is just as bad (and fast) as it was in the bad old days.The Free Software / Open Source world can do better.  Where youneed ACID compliance, safety, robustness, and flexibility, go
with PostgreSQL, it's a much better database.  Where you needspeed and don't care much about the other stuff, sqlite simplyhumiliates MySQL.As for the "trust"... most admins will go for the "fast" setup,
or even not touch the defaults.  Then something bad happens tothe data, and it's our fault.  Sigh.best,   Lalo Martins--  So many of our dreams at first seem impossible,
   then they seem improbable, and then, when we   summon the will, they soon become inevitable.--personal:  http://www.laranja.org/
technical:http://lalo.revisioncontrol.net/GNU: never give up freedom http://www.gnu.org/
___vos-d mailing listvos-d@interreality.orghttp://www.interreality.org/cgi-bin/mailman/listinfo/vos-d

___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d


[vos-d] Re: Re: next priorities; mySQL

2006-04-10 Thread Lalo Martins
On Sun, 09 Apr 2006 18:55:29 -0400, Reed Hedges wrote:
>> my personal goal for .24 would be refurbishing the sqlpersist machinery. I
>> just don't trust mysql at all ;-) 
> 
> What do you mean, you don't trust it?
> 
> What about PostgreSQL then?

I know MySQL is now a complete proper database system, with ACID and all. 
But up to just a few months ago, it was just a place to dump your data
that happened to (mostly) respond to SQL queries.  It gained so much
popularity because it was fast; but anyone who really cared
about this database stuff knew that it was faster because it was
incomplete.  Like, well, DOS is faster than WinXP.

And even now, at least last time I looked, the "completeness"
(ACID compliance and whatever else) is optional... the default
setup is just as bad (and fast) as it was in the bad old days.

The Free Software / Open Source world can do better.  Where you
need ACID compliance, safety, robustness, and flexibility, go
with PostgreSQL, it's a much better database.  Where you need
speed and don't care much about the other stuff, sqlite simply
humiliates MySQL.

As for the "trust"... most admins will go for the "fast" setup,
or even not touch the defaults.  Then something bad happens to
the data, and it's our fault.  Sigh.

best,
   Lalo Martins
-- 
  So many of our dreams at first seem impossible,
   then they seem improbable, and then, when we
   summon the will, they soon become inevitable.
--
personal:  http://www.laranja.org/
technical:http://lalo.revisioncontrol.net/
GNU: never give up freedom http://www.gnu.org/



___
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d