Transactions and foreign keys can be used with mysql. InnoDB tables make it
possible. They are optional in mysql version 3 (mysql-max), but are shipped
with mysql version 4.
As regards subselects, I think they should be supported starting at version
4.1, which is today at an alpha stage.
The problem is rather a Torque problem than a MySQL problem.
Is there any plan to have Torque use InnoDB tables ?
As regards the encoding problem, I personally use ISO-8859-1 or UTF-8 encoding
with MySQL with no problem. My first name for example contains a '�' which is
stored and rendered correctly. My OS is Linux RH 9.
Lo�c
On Monday 08 December 2003 12:07 pm, Scott Eade wrote:
> Akmal Sarhan wrote:
> >we are in the process of migrating our Turbine applications from MySql to
> > PostgreSQL and we would like to ask those who had some experience with
> > them to highlight the pros and cons if possible.
>
> I have just gone through this exercise - quite a difficult task, but
> IMHO worth it.
>
> The big pros are:
> + Transactions (though you can get this working in MySQL)
> + Enforcement of referential integrity
> + Support for subselects (though not via Criteria)
>
> For some good information see:
> http://nagoya.apache.org/wiki/apachewiki.cgi?TorqueProjectPages/PostgreSQLF
>AQ
>
> Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
