-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 24 October 2002 10:55, [EMAIL PROTECTED] wrote:
> Firebird will not block readers if some process is writting which, as you
> say, is common and it will only block writters that are modifying the same
> row.
yes, this is pretty standard fair. pgsql and oracle both provide sub-row
locking. for an interesting article on pgsql's MVCC:
http://www.linuxgazette.com/issue68/mitchell.html
> However it has a really neat feature that while you are in a
> transaction you are guaranteed that the data won't change on you. So if
> you are busy going some stuff and someone commits some changes you won't
> see it until you end your current transaction. Hopefully I explained it
> ok.
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
this is a common feature as well.
if you want something more interesting, PREPARE is a bit more exotic in the
open source RDBMS world.
> I just am finding that Firebird agrees with me a bit more.
viva la open source!
> My one complaint is the general confusion regarding documentation and the
> slowness of releases. I really am looking forward to some of the features
> added in 1.5 but who knows when that will come out.
this is one of the things i like about pgsql: the docs are plain and clear
(though i'd LOVE for more online example snippets, something that the
firebird docs have lots of), there are a few really good books available on
the topic and development is going VERY fast right now.
> Classic server runs from inetd which I'm not really a fan of. Super server
> is it's own server which means it's a bit snappier and it adds support for
> remote management.
ah, so classic means "crappy" and super means "what you'd expect from a modern
system". i'll remember to use super if i ever do a firebird install =)
> I believe they have some complete JDBC drivers that are supposedly quite
> stable.
do you know what type of JDBC they achieve? pgsql has a Type 4 (native Java,
implements the complete spec) ... on a related note, pgsql ships with
libraries for: C ( siplified, full and embedded SQL versions), C++, TCL,
ODBC, JDBC and Python. decent set of choices. firebird includes suport for a
few more language AFAIK.
speaking of which, i know that PHP4 has support for Interbase 6. is that equiv
to Firebird 1? the Interbase support in PHP is pretty lean, but adequate for
most usage.
> I think there are a few different sets though from different
> vendors so who knows.
>
> What is ACID compliance?
ACID => Atomicity, Consistency, Isolation, and Durability
most of this is handled by transactional capabilities, but in terms of an
RDBMs, it takes into consideration things like referential integreity. Cod's
Rules neatly sum things up:
http://members.aol.com/mbaddenda/art120.html
- --
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
"Everything should be made as simple as possible, but not simpler"
- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9uCxJ1rcusafx20MRAsOzAJsFcfWeCuaJgtpuGcf4Gsr0jXj47gCgrbJ5
AWAdmV130U1rbcxYYCwv2Eg=
=FHYt
-----END PGP SIGNATURE-----
