Transactional MySQL in PHP

gdestri

Hello Everybody,
We have a strange problem: we would like to port a PHP application,
originally developed using Oracle 8.1.X as DB (with all the oci_ functions),
to MySQL.
Unfortunately our application uses views (maybe they'll be available in version 4.1)
but also require the capability to explicitly commit any action in order to make
it permanent (or to rollback it).
1. Is it possibile, setting to FALSE the autocommit mode of MySQL, to achieve this
characteristic in PHP also?
2. Somebody suggest us the use of "Berkeley DB" but, as far as I know, Berkeley
DB is a non-SQL binary DB, not a MySQL connection API. Am I wrong? What does
this suggestion mean?

Any suggestion or link is welcome.

Many thanks in advance.

Regards,
Giulio Destri

Anon

Berkeley DB is a MySQL table type that supports transations. The default table type, MyISAM, does not.

[deleted]

Forget MySQL, use PostgreSQL. That has native transaction support and a lot more.

MySQL only has tables, selects and a few JOIN's. No subqueries, no views, no stored procedures, no foreign-key constraints, and no functional indexes.

MySQL has a habit of primising that the next release will give subqueries etc... but that's usually as close as they get to actually doing something.

Anon

Don't be so down on MySQL, vincent, it has its uses. :-)

I always refused to use PGSQL because it lacked full text indexing, replication and had an 8k row limit. Although I gather these have been addressed now, I still use MySQL because I'm used to it.

[deleted]

🙂

Yes MySQl has it's uses, but if you are coming from Oracle, MySQL is 'back to the stoneage'.

MySQL to Oracle is easy,
Oracle to MySQL is pure masochism.

Once you start using a real RDBMS, such as Postgres or Oracle, you get used to it's features like referencial constraints, cascading delete and functional indexing.
Compared to that, MySQL and it's FULLTEXT index is a mere flat-file interface. 🙂