e entry for
primary keys as follows:
primary_key_columns => [ 'user_id', 'user_id' ],
Which was extremely confusing.
It was just now that I removed the previously-created RDBO::User object
that I created by hand a while back, and now everything works properly.
Doh.
Than
The problem is more that the schema I have is large enough that I was
hoping to come up with a more straightforward example that properly
demonstrated the issue. ;)
Ovid wrote:
> - Original Message
> From: Peter Leonard <[EMAIL PROTECTED]>
>
>> I'm still
Hello all,
So I've been working with Rose::DB::Object::Loader for the last two
days, and I think I've found a bug with how foreign keys are handled
with a MySQL 5.0 database (InnoDB tables).
In short, when RDBO::Loader->make_classes() calls
$meta->auto_initialize(), and a foreign key relation
Hi Perrin,
Good call. :)
Rose::DB::Object::Cached would be a likely choice, except we're looking
at a multi-server cache - as Jonathan mentioned above, memcached is our
intended target.
Thanks,
Peter
Perrin Harkins wrote:
> Peter Leonard wrote:
>> I understand the compl
John,
Thank you for the quick reply.
I understand the complexity involved, and what we're looking for is the
quick storage & retrieval of the underlying data - I'll look at the
json/yaml serialization implementations.
Best,
Peter
John Siracusa wrote:
>
Hi all,
A second RDBO question - Does RDBO play nicely with Storable? Can I
freeze/thaw RDBO objects among various processes and get clean results?
(In a serial fashion, of course - I would not try to make updates to
the same object in several different places at once.)
Thank you
Hi All,
Going through the email archives, I found this thread, which effectively
covers the questions I have with respect to inheritance and RDBO (or any
OR layer for that matter):
http://www.mail-archive.com/rose-db-object@lists.sourceforge.net/msg00102.html
Given that this thread was from a
