On 5/1/06 7:53 PM, Guillermo Roditi wrote:
> use ing works just dandy, its when i relationship() the modules that it
> breaks : /
As I suspected, it was a timing issue for the circular dependencies. I'll
work on making the Loader account for these automatically in its generated
code. In the mean
use ing works just dandy, its when i relationship() the modules that it breaks : /thanks for the helpthe offending lines are commented out on the very last class. UserPropTypeBinIn order table definitions, classes, program using to test..
CREATE T
On 5/1/06 7:09 PM, Guillermo Roditi wrote:
> Is it because there is a circular relationship??? where every user has many
> props and many props have one user? it seems what heppens is that its
> trying to make a user object and so it makes the prop type object and then
> it tries to make a user o
OK, So I think I may have a clueI removed all the relationships and the 'use' code. Now I have something like this (from the original 33 tables)Tablesusers, user_prop_type_bin, user_prop_type_float, user_prop_types, user_props
with a relation of user -> user_prop_type_* it works flawlesslyas so
OK I spoke to soon. The errors are back on the rest of my codebase. If i take the __PACKAGE__->meta->relationships(...) lines it seems to be fine. I think it may be an issue with the convention manager. I thought I named everything according to standard conventions but all of a sudden i guess maybe
On 5/1/06, Guillermo Roditi <[EMAIL PROTECTED]> wrote:
Hi, I am having a little trouble with Rose::DB::Object.
I keep getting the error below and I am not entirely sure what it means...
Dos it mean that it couldnt guess the foreign class name ?
Are you using the Loader? If so, can you provide
Hmmm. I actually found it. a misspelling while defining a relationship. I grepd through Manager.pm to figure it out. it always happens that as soon as i get frustrated enough to post to a list i end up finding the error 3 seconds after i post. grrr.
On 5/1/06, John Siracusa <[EMAIL PROTECTED]> wrot
Hi, I am having a little trouble with Rose::DB::Object.I keep getting the error below and I am not entirely sure what it means... Dos it mean that it couldnt guess the foreign class name ?Use of uninitialized value in concatenation (.) or string at
/usr/local/lib/perl5/site_perl/5.8.7/Rose/
On 5/1/06, Guillermo Roditi <[EMAIL PROTECTED]> wrote:
Is there any reason why I wouldn't want to use Rose::DB::Object::Cached for
everything instead of just using Rose::DB:: Object as a base for my
database table classes?
I think the description section from the POD contains some very good
rea
Is there any reason why I wouldn't want to use Rose::DB::Object::Cached for everything instead of just using Rose::DB:: Object as a base for my database table classes?
On 5/1/06 3:06 AM, Michael Lackhoff wrote:
> So the bottom line is that there was a recent bugfix that is
> important for many to many relationships.
I don't remember that one, but there have been so many updates that I've
kind of lost track. Anyway, I'm glad the current version works correctly :
On 30 Apr 2006, John Siracusa wrote:
> I can't think of any reason this would behave any differently under
> mod_perl.
You are right. Sorry, it was another one of these silly mistakes. I
have two perl installations, one as a "normal" installation and
another one that came with apache, this is t
12 matches
Mail list logo
