As most of you know, the Engine Vendor Advisory Board was setup by Oracle under terms that Oracle specified for themselves when acquiring MySQL. I am referring to point number 8, on the 10 point list that played a major role in quieting nervous Bureaucrats in Europe.
PrimeBase Technologies is a member of the Board and so far we have heard nothing of a meeting this year.
Has the Board been quietly disbanded?
If so, what does this mean for the other promises on Oracles list...
UPDATE: We are in contact with Oracle concerning this. I will keep you all posted. Hopefully it was just a communications error.
PrimeBase XT (PBXT) is a transactional storage engine for MySQL which can be loaded dynamically by the pluggable storage engine API of MySQL 5.1. It has been designed for modern, web-based, high concurrency environments. Full MVCC (multi-version concurrency control) support and a unique "write-once" strategy make PBXT particularly effective under heavy update loads.
Friday, September 30, 2011
Tuesday, April 12, 2011
PBXT "Secrets" at the MySQL Conference
In my presentation tomorrow at the MySQL Conference I plan to talk about some aspects of PBXT that I have never spoken about before. Here are the details of the presentation:
Update on the PBXT Storage Engine
10:50am Wednesday, 04/13/2011
Location: Ballroom D
10:50am Wednesday, 04/13/2011
Location: Ballroom D
Of course nothing about the engine is really a secret, if you are prepared to read the code. But who does that right? I am pretty sure that not even developers of other engines have spent much time (if any) on that.
But really, there are some gems stuck away in those X 1000 lines of code, and I plan to pick out a few tomorrow and show them to you. So don't miss it! :)
But really, there are some gems stuck away in those X 1000 lines of code, and I plan to pick out a few tomorrow and show them to you. So don't miss it! :)
Subscribe to:
Posts (Atom)