Alexander Mette wrote:
>this night toggg added more compatibility for PostgreSQL.
>Sweetest part of it is imho an addition to the
>db/convertscriptsmysql3topgsql72.php, that automagically adds the - in Tiki
>used and in PostgreSQL 'missing' - function right(), when running
To be more exact db/convertscripts/convertsqls.sh calls, in order to
create db/tiki_postgresql.sql db/convertscripts/mysql3topgsql72.php wich
then incorporates the CREATE FUNCTIONs in the former DB creation script.
These functions are stored in the DB and won't alter PostgreSQL outer of it.
The goal is to get pg running without to change the queries (and
localize them) so we won't touch the current running mySQL. Only
PostgreSQL will see what (hopefully good)
>Same shall happen for other functions, that make problems with pgsql-compat.
I added the aggregate function MAX(boolean) which was quite a blocker
there, and also not so easy.
I would remind that all these are some hacks to cope with the non
conformance of mySQL to the standards, so better keep on right syntax
One thing "we" could not turn around is the case sensitivness in column
names. Unfortunately, mysql is very permissive on it, but PostgrSQL is
naturally virtuous (especially with the adodb mechanisms).
So, we have to correct each query where the case of column names was not
respected. So far tested, seems very few cases, but please respect this
rule. Use column names with the right lower/uppercases.
>So, please: Report any potentially 'missing' functions here, that come to your
>mind! Thanks! :)
Hope we can correct them on a global, environment respectfull way the same
bertrand "toggg" Gugger