[RDBO] feature request -> is not

2007-04-30 Thread Jonathan Vanasco
i'd like to see an "is not" operator

something like:
'!NAME' => undef# COLUMN IS NOT NULL

under postgres, booleans behave as such:

example table
create table test  ( id integer not null , is_selected boolean );
insert into test ( id , is_selected ) values ( 1 , NULL );
insert into test ( id , is_selected ) values ( 2 , true );
insert into test ( id , is_selected ) values ( 3 , false );

get them all:
select * from test;
returns: 1,2,3

get not true:
select * from test where is_selected is not true;
returns 1,3

get not false:
select * from test where is_selected is not false;
returns 1, 2

current rose support can't do that.  the closest it gets is this:

select * from test where is_selected <> false ;
returns 2

select * from test where not(is_selected = false) ;
returns 2

that said, if the following two OP could be added to query builder:
is not
is  ( just for standardization )

that  would be great :)


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object


Re: [RDBO] Release soon

2007-04-30 Thread Jonathan Vanasco

On Apr 30, 2007, at 4:37 PM, John Siracusa wrote:

> Even though there are a bunch of things on my short-term list that I
> haven't gotten to, the change list is already quite large and I want
> to cut a release soon (it will be 0.764).  Is there any feature that I
> previously mentioned I'd get to in the short term and that someone is
> dying to have?  Speak now or wait until 0.765!
>
> (I think I've fixed all known bugs in SVN.  Let me know if I haven't.)
> -John


i could have the object_tree stuff finalized by tomorrow if you'd like.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object


[RDBO] Release soon

2007-04-30 Thread John Siracusa
Even though there are a bunch of things on my short-term list that I
haven't gotten to, the change list is already quite large and I want
to cut a release soon (it will be 0.764).  Is there any feature that I
previously mentioned I'd get to in the short term and that someone is
dying to have?  Speak now or wait until 0.765!

(I think I've fixed all known bugs in SVN.  Let me know if I haven't.)
-John

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object


Re: [RDBO] One to Optional One relationships

2007-04-30 Thread John Siracusa
On 4/26/07, Ovid <[EMAIL PROTECTED]> wrote:
>> Unfortunately, in your example, that will fail (I think) because a column in
>> the left-hand side of the column_map in the suspended relationship
is part of
>> the primary key of the server class.  I'll try to add a fix for this soon.
>> Any strong feelings about how it *should* behave?
>>
> Yup.  Same behavior.  Darn.  I can work around this with a 'one to many'
> relationship, but that's more pain than it's worth.  I'm just going to delete
> the relationship and code everything by hand.
>
> And I can't say I have strong feelings about how this should behave. 'one to
> optional one' should just allow me to set up an 'optional' second class to be
> associated with the primary class and delete the second class, as needed.
> e.g., if 'A' has an optional 'B', the existence or non-existence of 'B' should
> have no material affect on 'A'.

Okay, this is fixed in SVN.  Now the key columns are only set to undef
if the "referential_integrity" (for fks) or "required" (for
relationships) attribute is true.  And even when the key columns are
set to undef, if a column is also part of a primary key, it is not set
to undef.

-John

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object