Re: Database choices
Re: Database choices
- Subject: Re: Database choices
- From: Guido Neitzer <email@hidden>
- Date: Mon, 29 Oct 2007 19:25:48 -0600
On 29.10.2007, at 17:01, Q wrote:
Until postgresql gets a solid clustering solution, frontbase comes
out in front in my opinion.
Depends a bit on your workload and your requirements.
Where PostgreSQL shines:
+ insert speed
+ indexing speed (helps inserting)
+ has "vacuum full", to shrink the footprint of the db on disk
+ has a lots of parameters you can tweak to get the best out of it
+ the query planner is extremely good, even for very complex queries
+ support on the mailing list is very good
+ creating indexes for case-sensitive or case-insensitive queries
+ query planner analysis tools ("explain analyze select ...")
Where FrontBase shines:
+ ease of use / installation
+ backup (backup sucks with PostgreSQL and is amazingly easy with
FrontBase)
+ clustering, replication
+ support if you get a support plan (and without a plan if you found
a real bug)
+ database encryption
+ JDBC driver (re-connecting, server fail-over and so on)
+ in memory caching for tables / indexes
+ fulltext indexing (LookSee)
The remaining problem I had with FrontBase is the sometimes slow
inserts on tables with not so many columns, but a lot of rows (over 5
millions at the moment) and a 24 byte primary key. It seems that
maintaining the pk index is very expensive for that kind of column.
Maybe a long would be better here. Also the integrated "select
unique" can "only" return 32 bit integers, not longs like the
PostgreSQL sequences can. Not necessarily a problem if you can use
e.g. the Wonder ERXLongPrimaryKeyFactory for that.
Also adding columns in large tables often ends up in table bloat,
which is REALLY hard to get rid of as I can't reduce it's size on
disk, even if you don't provide a default value or so (Is that still
the case?).
So, it depends on what you need. If you want a database server, that
runs out of the box with nearly perfect backup and clustering support
- get FrontBase. If you need to tweak a LOT of things to get the best
performance out of a large and complex database - I'd use PostgreSQL.
To put it that way: I love to have both databases around as I can use
both their strengths.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden