Re: [SQLObject] RelatedJoin bug

[Edmund L. <el...@in...>]

Ian Bicking wrote:

> You can put do createTable(createJoinTables=False).  Otherwise it should
> create the join table when you create the table that's alphabetically
> first (so both createTables don't create the shared table).  Is that not
> working for you?

No, I just didn't think of doing this. I will now!

> Why would there by a null value?  Each row is a relationship, so a row
> with a null should just be deleted.  Maybe it's because you are using it
> all funny like, with a triple join... hmm... well, I made a change that
> I think should work.  I also got rid of the funny behavior you got when
> you accidentally instantiated an object with an id of None.

Yes, it seems wierd the way I do it, but not really. What I'm trying to 
do (using my Cat/Dog/Person example) is capture the relationship between 
a person and all his/her animals within the same mapping table. There 
are a variety of legitimate reasons for doing so.

When you do this, a null value in one row need not necessarily indicate 
invalid data. I do have a check constraint to ensure that each row has 
at least pair of non-null values.

...Edmund.