I managed to stick RT schema into Postgres. There were two problems: User
and Right are reserved words in SQL3 (and obviously in postgres), I
changed that to RUser and RRight (yeah, so I suck in naming conventions).
Now, I need to change all the queries that refer to these fields. I found
two, but I think there are more. At that point, I lost my patience and
left it for the ‘next time’
Jesse, can you rename these fields to something sensible and adjust the
queries, and send appropriate big warning to whoever is using RT2 to
rename their columns?
Another thing that might cause pain is fact that mysql deals with
timestamp as numeric YYYYMMDDHHMMSS and postgres and standard way is of
course ‘DD/MM/YY’ (or variations, but never numeric)
-alexOn Tue, 6 Jun 2000, Jesse wrote:
Well, I wouldn’t quite phrase it like that, but the gist is right.
We’re actively soliciting developer help to port RT’s DBIx routines
and schema to databases other than Mysql. So far, we’ve got someone signed up
to do DB2 and I’ve heard mumbles about postgres and oracle…Anyone want to
hack on interbase support?
On Tue, Jun 06, 2000 at 10:17:08AM +0200, Tobias Brox wrote:
Do you have any plans to support it in the future?
We use DBI and only valid SQL in RT2, so porting it to other DBMS’es
should be pretty straight-forward. However, neither me nor Jesse will do
any porting ourself, we rely on the folks that needs to use other DBMS’es
to fix this themselves. Anyway, I might mention your DBMS as an
alternative in the README.
“The trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.”
Rt-devel mailing list