[AccessD] MySQL PBXT, transactional engine

Hi Jim

Thanks, let's learn from his findings. However, I didn't mean to hold anything back - I haven't worked with it myself.
But the PBXT engine seems to be a proven product from PrimeBase while the new Falcon engine is still in beta.

/gustav

>>> accessd at shaw.ca 09-03-2007 23:25 >>>
Hi Gustav:

Further to my comments, after forwarding along your email to my son-in-law,
it appears that he had not heard of this PBXT advancement and is currently
holding the launch of their web site until further investigation...   

Good timing Gustav.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Friday, March 09, 2007 10:12 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] MySQL PBXT, transactional engine

Hi Gustav:

My son-in-law is in Britain, at this moment and he phoned last night from
work at about 2pm here or 10pm there as they are putting the finally touches
to a large web site. The BE DB is the latest MySQL server engines. Actually
it is using 3 MySQL engines. I would send the link but as the 10pm time
would suggest things are running behind schedule.... but he keeps saying
that the new MySQL is 'brilliant'.

Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Friday, March 09, 2007 5:42 AM
To: accessd at databaseadvisors.com 
Subject: [AccessD] MySQL PBXT, transactional engine

Hi all

This engine is quite interesting. Features no database file, only log files,
thus no record view locks, no other than physical limits on table size, no
fixed record size, and zero time for recovery.

<quote>

Paul McCullagh from PrimeBase (www.primebase.com) has created the PBXT
transactional storage engine for MySQL. PBXT is an ACID compliant
transaction engine that offers all the right features for MySQL users who
are on the hunt for an engine to keep their transactional data safe. PBXT
sports crash recovery, unlimited row-level locking, MVCC, foreign
keys/server-enforced referential integrity, automatic storage management,
minimal configuration setup, and online backup support. 

  http://dev.mysql.com/tech-resources/articles/pbxt-storage-engine.html 

</quote>

Also, a white paper is for download which explains this in full:
  
  http://www.primebase.com/xt/download/pbxt_white_paper.pdf 

/gustav