[rt-devel] rt3 with oracle

[Brook Schofield]

On Thursday, April 17, 2003, at 06:36  PM, Jeroen Ruigrok/asmodai wrote:
> -On [20030417 10:32], Brook Schofield (B.Schofield at griffith.edu.au) 
> wrote:
>> the only problem is that it really shouldn't be setup like this. I'm 
>> going
>> to look at the initialize-database under MySQL in some detail. And 
>> workout
>> what it is doing under those circumstances - and see how/if the 
>> change to
>> Oracle is breaking it.
>
> Wouldn't PostgreSQL's schema be more of use since it is more a real
> database in terms as Oracle/DB2/Sybase are?

I'm going to be looking at what the actual SQL INSERTS look like under 
MySQL (because I have that installed) and then compare them with those 
of the Oracle version. The only difference is the change in the Handler 
used by DBIx::SearchBuilder (I hope). This should result in exactly the 
same data being inserted into MySQL as is inserted into Oracle - which 
would beg the question: "Why doesn't MySQL error with this schema?"

CREATE TABLE GroupMembers (
   id INTEGER NOT NULL  AUTO_INCREMENT,
   GroupId integer NOT NULL DEFAULT 0,
   MemberId integer NOT NULL DEFAULT 0,  #Foreign key to Principals
   PRIMARY KEY (id)
) TYPE=InnoDB;

I've change the Oracle schema to allow NULL values in GroupId - and the 
data insertion works like a treat. So I'm still on the path of trying 
to find out why a NULL value is trying to be inserted. I'm getting 
closer. I also found the Handler trying to perform LIMIT 1 at the end 
of an SQL query (which should be replaced with the Oracle specific 
LIMIT syntax - which is to verbose to detail here).

Stay tuned!

-Brook