in reply to Re^3: DBIx::Class questions
in thread DBIx::Class questions

Yes, you should create a DBIx::Class file for each table, including the ones used to just link across, for a many-to-many (Funnily enough, theres a bridge method that creates many-to-many rels for you).

How are the system/role/user tables actually set up? Given a "system", using SQL, how do you find the point_of_contact? That might be the easiest way of translating it to DBIx::Class.

As for the elements, I don't know how they look like in the database either, can you maybe just post your create table statements, and we can go on from there?

C.

Replies are listed 'Best First'.
Re^5: DBIx::Class questions
by jimbus (Friar) on Oct 13, 2006 at 12:33 UTC

    Unfortunately, I've invested more than a week into catalyst and trying to learn DBIx and have little to show for it. I'm at the point where I need to admit defeat and go with what I know... building psuedo-objects in my business logic layer and building my own plain, dirty sql tables and displaying with mod_perl and mason... at least I've progressed to the point that I know longer have my business logic wrapped up in my view code. :)

    Perhaps I'll try again later with something not so large and see if I can revisit this again later... but those sound like famous last words :(

    --Jimbus aka Jim Babcock
    Wireless Data Engineer and Geek Wannabe
    jim-dot-babcock-at-usa-dot-com
[reply]

In Section Seekers of Perl Wisdom