Hi,
the admin functions are now working to about 70%, and I hope to put up a patch file for the admin directory quite soon. I cannot check if I have accidently killed any mysql functions, so it will need checking.
points:
1: the code in SQL inserts must now always include $dbIDnull instead of '%' to be postgresql compatible.
2: postgresql does not like non-set variables being used in SQL statements- mysql does not seem to worry.
3: I have changed the table "user" to "puser" when using postgresql. Perhaps it would be easier to change this name for everything at the next major version.
4: At present I dont see how the automatic postgresql database creation at installation can work. Perhaps somebody has an idea. The automatic table creation is however ok and working.
regards
john
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
... but there are also changes with this prefix-db_query()
In some cases i.e. itemID as name of a column gets also a prefix :-(
- First possibilty is adding the table name to itemID.
- Second way is to build a better replace-instruction in db_query().
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
the admin functions are now working to about 70%, and I hope to put up a patch file for the admin directory quite soon. I cannot check if I have accidently killed any mysql functions, so it will need checking.
points:
1: the code in SQL inserts must now always include $dbIDnull instead of '%' to be postgresql compatible.
2: postgresql does not like non-set variables being used in SQL statements- mysql does not seem to worry.
3: I have changed the table "user" to "puser" when using postgresql. Perhaps it would be easier to change this name for everything at the next major version.
4: At present I dont see how the automatic postgresql database creation at installation can work. Perhaps somebody has an idea. The automatic table creation is however ok and working.
regards
john
RE 3:) Perhaps the new function db_query() is useable for it; it makes possible to add prefix to table-names without changing queries.
Thanks for your help.
Good idea.
I have however had to give it up, as the table name appears in so many different positions in the SQL with different words before and afterward.
... but there are also changes with this prefix-db_query()
In some cases i.e. itemID as name of a column gets also a prefix :-(
- First possibilty is adding the table name to itemID.
- Second way is to build a better replace-instruction in db_query().