On 6/4/07, John Siracusa <[EMAIL PROTECTED]> wrote:
On 6/3/07 5:20 PM, I?ja Ketris wrote:
> I wonder how the module decides about foreign keys over relationships.
If it's there's a real foreign key constraint in the database, the Loader
make a foreign key in the RDBO class.
How is this poss
On 6/3/07 9:11 PM, Jonathan Vanasco wrote:
> add_unique_keys seems weird too...
>
> by the name alone, one would expect
>
> add_unique_key( $uk );
> add_unique_keys( $uk1, $uk2 );
That should work fine, provided $uk1 and $uk1 are
Rose::DB::Object::Metadata::UniqueKey objects.
> suffice to say,
sorry this took so long to respond -- been too busy on the business
side of work, little time for code.
On May 18, 2007, at 2:21 PM, John Siracusa wrote:
> I think it's pretty clear given that the table definition is right
> above it, and contains:
>
> UNIQUE(product_id, region)
ok. th
On 6/3/07 5:20 PM, I?ja Ketris wrote:
> I wonder how the module decides about foreign keys over relationships.
If it's there's a real foreign key constraint in the database, the Loader
make a foreign key in the RDBO class.
-John
-
Hello,
I am trying to reproduce the example from Rose::DB::Object::Loader
documentation (adapted for use with SQLite), and it works the way I expect.
When I dump generated classes with make_modules, I see smtg like
relationships => [
products => {
class => 'My::Corp::P
