Hello,
Interbase ( www.interbase.com ) is the newest open-source SQL database.
It’s a mature, formerly commercial program that supports quite a bit
more of the SQL specification than MYSQL. Or Postgres.
Do you have any plans to support it in the future?
Thank you!
Chris
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.”
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?
JesseOn 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.”
- Bertrand Russell
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
“It’s buried in the desert, got sand in it, melts Nazis. You know,
the Ark of the Covenant” – siva
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?Jesse
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.”
- Bertrand Russell
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
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)
That must be wrong? The standard SQL timestamp follow the ISO standard;
“YYYY-MM-DD HH:MM:SS”. mysql can accept this as an input, but not in the
output. I already have a solution up and running that should be
compatible, I just haven’t installed it (in DBIx/Record.pm - except for
duedate, all dates we need will be true timestamps, either LastUpdated or
Created) yet.
It should be trivial to replace User with RTUser and Right with Permission
all over the system.
“The trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.”
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)That must be wrong? The standard SQL timestamp follow the ISO standard;
“YYYY-MM-DD HH:MM:SS”. mysql can accept this as an input, but not in the
output. I already have a solution up and running that should be
compatible, I just haven’t installed it (in DBIx/Record.pm - except for
duedate, all dates we need will be true timestamps, either LastUpdated or
Created) yet.
Great!
It should be trivial to replace User with RTUser and Right with Permission
all over the system.
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…
Thanks!
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…
sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply. 
Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
“The trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.”
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply.Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
Quite honestly, I can’t, because I do not use mysql, and don’t want to
bother installing it to test it, and with postgres, there are still a lot
of things that are borken, so i “can’t” be sure it works…
I’d be more confident if someone who has a bigger clue about RT performs
that change
Thanks
-alex
I’d be more confident if someone who has a bigger clue about RT performs
that change
Ok, I’ll do that … just not today
“The trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.”
Someone yesterday weighed in with a 1.0.x problem where they had too many
tickets in their queue to display. I have a 'show blah tickets/screen’
function almost done, and am testing it. How many tickets do you have in
your queue?
Hrm… well, ok, I guess it doesn’t matter, but I’d still like to know.
Thanks,
Blue Lang Unix Systems Admin
QSP, Inc., 3200 Atlantic Ave, Ste 100, Raleigh, NC, 27604
Home: 919 835 1540 Work: 919 875 6994 Fax: 919 872 4015Alex, are you talking about RT 1.0 or RT 2.0?
The changes won’t make it into 1.0, but 2.0 should definitely get fixed.On Tue, Jun 06, 2000 at 12:10:08PM -0400, Alex Pilosov wrote:
On Tue, 6 Jun 2000, Tobias Brox wrote:
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply.Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
Quite honestly, I can’t, because I do not use mysql, and don’t want to
bother installing it to test it, and with postgres, there are still a lot
of things that are borken, so i “can’t” be sure it works…I’d be more confident if someone who has a bigger clue about RT performs
that changeThanks
-alex
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
I have images of Marc in well worn combat fatigues, covered in mud,
sweat and blood, knife in one hand and PSION int he other, being
restrained by several other people, screaming “Let me at it!
Just let me at it!” Eichin standing calmly by with something
automated, milspec, and likely recoilless.
-xiphmont on opensource peer review
2.0
-alexOn Tue, 6 Jun 2000, Jesse wrote:
Alex, are you talking about RT 1.0 or RT 2.0?
The changes won’t make it into 1.0, but 2.0 should definitely get fixed.On Tue, Jun 06, 2000 at 12:10:08PM -0400, Alex Pilosov wrote:
On Tue, 6 Jun 2000, Tobias Brox wrote:
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply.Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
Quite honestly, I can’t, because I do not use mysql, and don’t want to
bother installing it to test it, and with postgres, there are still a lot
of things that are borken, so i “can’t” be sure it works…I’d be more confident if someone who has a bigger clue about RT performs
that changeThanks
-alex
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Hrm. The only place I see “User” and “Right” mentioned is in the
QueueACL table. Am I not looking hard enough? That table is
unused and slated for destruction.
jesseOn Tue, Jun 06, 2000 at 12:45:49PM -0400, Alex Pilosov wrote:
2.0
-alex
On Tue, 6 Jun 2000, Jesse wrote:
Alex, are you talking about RT 1.0 or RT 2.0?
The changes won’t make it into 1.0, but 2.0 should definitely get fixed.On Tue, Jun 06, 2000 at 12:10:08PM -0400, Alex Pilosov wrote:
On Tue, 6 Jun 2000, Tobias Brox wrote:
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply.Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
Quite honestly, I can’t, because I do not use mysql, and don’t want to
bother installing it to test it, and with postgres, there are still a lot
of things that are borken, so i “can’t” be sure it works…I’d be more confident if someone who has a bigger clue about RT performs
that changeThanks
-alex
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
Gur SOV jnagf gb znxr guvf fvt vyyrtny.
Yep, that’s the table. If its unused, the better, but I still saw a few
references to it in perl code. So let’s get rid of the table and
references?
-alexOn Tue, 6 Jun 2000, Jesse wrote:
Hrm. The only place I see “User” and “Right” mentioned is in the
QueueACL table. Am I not looking hard enough? That table is
unused and slated for destruction.jesse
On Tue, Jun 06, 2000 at 12:45:49PM -0400, Alex Pilosov wrote:
2.0
-alex
On Tue, 6 Jun 2000, Jesse wrote:
Alex, are you talking about RT 1.0 or RT 2.0?
The changes won’t make it into 1.0, but 2.0 should definitely get fixed.On Tue, Jun 06, 2000 at 12:10:08PM -0400, Alex Pilosov wrote:
On Tue, 6 Jun 2000, Tobias Brox wrote:
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply.Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
Quite honestly, I can’t, because I do not use mysql, and don’t want to
bother installing it to test it, and with postgres, there are still a lot
of things that are borken, so i “can’t” be sure it works…I’d be more confident if someone who has a bigger clue about RT performs
that changeThanks
-alex
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
It will come. Once I get back from vacation, I get to hack on ACLs
The only reference i see to that table in the 1.3/2.0 codebase is in UpgradeRT,
which is out of date and not really “part” of RT2 itself…On Tue, Jun 06, 2000 at 12:50:53PM -0400, Alex Pilosov wrote:
Yep, that’s the table. If its unused, the better, but I still saw a few
references to it in perl code. So let’s get rid of the table and
references?-alex
On Tue, 6 Jun 2000, Jesse wrote:
Hrm. The only place I see “User” and “Right” mentioned is in the
QueueACL table. Am I not looking hard enough? That table is
unused and slated for destruction.jesseOn Tue, Jun 06, 2000 at 12:45:49PM -0400, Alex Pilosov wrote:
2.0
-alex
On Tue, 6 Jun 2000, Jesse wrote:
Alex, are you talking about RT 1.0 or RT 2.0?
The changes won’t make it into 1.0, but 2.0 should definitely get fixed.On Tue, Jun 06, 2000 at 12:10:08PM -0400, Alex Pilosov wrote:
On Tue, 6 Jun 2000, Tobias Brox wrote:
Not trivial enough for me, there are hundreds of occurences of ‘User’ in
RT code (sql is case-insensitive)…sql is, but MySQL isn’t. So there is no references of ‘user’ or ‘USER’
that reffers to the SQL table in the code. Simply.Many method names correspond to the column names.
I don’t think it’s that difficult to do a controlled search-and-replace
all over the code. I don’t think it will hurt if all instances of $User
becomes $RTUser. Just be sure to check that everything actually is
working before submitting a patch.
Quite honestly, I can’t, because I do not use mysql, and don’t want to
bother installing it to test it, and with postgres, there are still a lot
of things that are borken, so i “can’t” be sure it works…I’d be more confident if someone who has a bigger clue about RT performs
that changeThanks
-alex
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
I think co-ordinating 1000 prima donnas living all over the world will be as
easy as herding cats…" – Andy Tanenbaum on the linux development model, 1992
The only reference i see to that table in the 1.3/2.0 codebase is in UpgradeRT,
which is out of date and not really “part” of RT2 itself…
Oh, UpgradeRT is hopelessly outdated. That’s one thing I have to deal
with, for sure. But I’ll wait until Jesse has fixed the ACLs …
“The trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.”