[RDBO] Downloadable archive of Rose mailing lists?

2005-11-22 Thread Torsten Seemann
interface only? Any help appreciated, -- Torsten Seemann <[EMAIL PROTECTED]> Victorian Bioinformatics Consortium --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free C

Re: [RDBO] column_type_class

2005-11-30 Thread Torsten Seemann
ger representations, so if switch=='on' then 0+switch==2. Ech. http://dev.mysql.com/doc/refman/4.1/en/enum.html -- Torsten Seemann <[EMAIL PROTECTED]> Victorian Bioinformatics Consortium --- This SF.net email is sponso

Re: [RDBO] column_type_class

2005-12-01 Thread Torsten Seemann
On Wed, 2005-11-30 at 23:43 -0500, John Siracusa wrote: > On 11/30/05 11:29 PM, Torsten Seemann wrote: > > Just keep in mind that MySQL 'ENUM' stores them as integers, and that > > integer is ALWAYS reserved to store the empty string '' as 0. So even if &g

[RDBO] ARRAY column types in Rose::DB

2005-12-01 Thread Torsten Seemann
uot;bar bie",1.61818}' ? What happens if someone manually shifted an element onto the front of a Pg 1-D array, and the string was changed to '[-1:4]{.}' does your parser handle that? What sort of querying can be done on ARRAY types? cf. Pg's ANY() and ALL() function

Re: [RDBO] ARRAY column types in Rose::DB

2005-12-01 Thread Torsten Seemann
alue 4 wasabi=> select * from atest where 4 = ALL(x); x - {4,4,4,4,4} (1 row) # selected rows where every element in the array had value 4 NOTE: you must write 4=ANY(x) -- ANY(x)=4 fails syntax Lots more information here: http://www.postgresql.org/docs/8.1/interactive/a

Re: [RDBO] ARRAY column types in Rose::DB

2005-12-03 Thread Torsten Seemann
John, wasabi=> select * from atest; x - [0:3]={3,4,5,6} So in this case you'd like the Perl array to be [ 3, 4, 5, 6 ], correct? I'd be happy with that. In fact I wish Pg had a separate LIST type as opposed to ARRAY type, where indices were irrelevant. In Perl can you

Re: [RDBO] Arbitrary-depth joins: vote on syntax

2005-12-24 Thread Torsten Seemann
With the new "arbitrary-depth joins" feature, you can join as deep as you'd like. The syntax I'm using for this feature right now is a chain of relationship names, with "." between each one. Example: $products = Product::Manager->get_products( require_objects => [ 'vendor.addresse

Re: [RDBO] RDBO::Manager->get_objects in list context

2005-12-24 Thread Torsten Seemann
I hate wantarray. It's a constant source of bugs and makes testing more complicated. I prefer methods that consistently return the same thing. my @foo = Bar->search(baz => 1) || die "no baz found"; That will not give the list context return, but rather the scalar return, which is an iterator in