--On Mittwoch, 24. November 2004 9:32 Uhr +0000 John Poltorak <jp@warpix.org> wrote:

OK, so as far as you are concerned Postgres itself is a better database, but does it make any difference as far as Zope is concerned? And what changes, if any, would be required to Zope if changing from one to the other?

Changing the DB affects your application and not Zope except you have to install another database adapter. If you use DB specific SQL or features then this is a problem of your application. -aj

Am Mittwoch, den 24.11.2004, 13:50 +0100 schrieb Hermann Himmelbauer:

On Tuesday 23 November 2004 23:54, John Poltorak wrote:

...

I'd like to connect up a database to Zope, but have no real database experience. My choice is between MySQL and PostgreSQL.

Don't leave out MySQL's "MaxDB", formerly "SAPDB" in your choice.

...

Is there any difference between them from Zope's POV?

Yes and no: If you don't use database specific things, there should be no difference. But

This would only be true if both database support SQL(xx) but this is not really the case for mySQL. So with mysql you end up with a lot of DB specific stuff to do the trivial things (and still not getting it right) SELECT a,b FROM foo would be ok, but beware the inserts, constraints, ...

very often you will want/need database specifics.

At least in the cases where you need a RDBMS at all :-)

Everything I've read says that MySQL is much faster, and matches Oracle for speed... If your going to do heavy lifting on a budget... something to consider. An advantage of MySQL is that it doesn't encourage you to code in the database... stored procedures et al, are nice, but not as easy to manage as keeping it in the app code. Just an opinion, -Jon Cyr Philip Kilner wrote:

Hi All,

Hermann Himmelbauer wrote:

...

...

I'd like to connect up a database to Zope, but have no real database experience. My choice is between MySQL and PostgreSQL.

Don't leave out MySQL's "MaxDB", formerly "SAPDB" in your choice.

...or Firebird (http://firebird.sf.net), which has a good Zope DA.

HTH

Cheers,

PhilK _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

Hi, Gosh... Never Ever... I guess MySQL should close up shop... Your question of Databases is actually quite personal to your project... What do you need? Speed/Throughput, ease-of-use, help resources, deployment tools, robust SQL... The nice thing about MySQL, PostgreSQL, and Firebird, is they are all avaiable to try out. I like MySQL's minimalist approach for RDBMS, it fits the needs of a project of mine, and the damn thing screams. You should hit the MySQL, PostgreSQL, etc. mailing lists, and ask a few questions with your needs in mind. Spend some time outlining your needs, and you'll reap the benefits down the road... -Jon Make a list Tino Wildenhain wrote:

Hi,

Am Montag, den 29.11.2004, 15:33 -0500 schrieb Jonathan Cyr:

...

Everything I've read says that MySQL is much faster, and matches Oracle for speed... If your going to do heavy lifting on a budget... something to consider.

Never ever. Well, if you do read only simple selects. But then you can also store the data in Files and use memory mapping.

IF you want to do heavy inserts while complex selects are going on you see a lot of speed differences in databases.

Not to mention what happens if you are so old fashioned to expect you get out of the database what you put in - and not whatever the database decides to let you see *wink* ;)

...

An advantage of MySQL is that it doesn't encourage you to code in the database... stored procedures et al, are nice, but not as easy to manage as keeping it in the app code.

This sounds like an euphemism :-) "Doesnt encourage" is better then the bare truth: "Does not allow" ;)

Well, for playing around, store some simple unimportant things, mySQL is certainly ok and a bit faster then Gadfly.

If you love your data, want to learn SQL, want a unique interface (from different applications) to your data, want security, dont have only trivial queries, well, then maybe you want another database.

Regards Tino

On Monday 29 November 2004 21:33, Jonathan Cyr wrote:

Everything I've read says that MySQL is much faster, and matches Oracle for speed... If your going to do heavy lifting on a budget... something to consider.

Well, that's not entirely true: Although MySQL is very fast with simple select statements, this is not the case with very complicated queries with multiple table joins etc.

An advantage of MySQL is that it doesn't encourage you to code in the database... stored procedures et al, are nice, but not as easy to manage as keeping it in the app code.

"Not encourage" is here equal to "does not support". Stored procedures have it's place in the database world. Yes, they do have their drawbacks and it should be carefully considered when to use them. But this does not mean that their usage always lead to a bad design. Best Regards, Hermann -- x1@aon.at GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7