On 9/18/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> the problem is that i need to limit a query to where
>
> a.1.b.1.FIELD = a.2.a.1.a.FIELD
Have you tried using eq_sql?
'a.1.b.1.FIELD' => { eq_sql => 'tN.FIELD' },
-John
On Sep 18, 2006, at 3:31 PM, Jonathan Vanasco wrote:
> a.1.b.1.FIELD = a.2.a.1.a.FIELD
>
> rose doesn't seem to support this outright
>
> anyone have a clue how i can coerce this?
Sorry, I forgot to add that this is within a nested conditonal
WHERE
(
a.1.b.1.FIELD_
i have a rather complex object query that pulls in 8 rose db objects
during a manager query
it kind of looks like this:
a.1.b.1
a.1.a
a.1
a
a.2
a.2.a
a.2.a.1
a.2.a.1.
On Monday 18 September 2006 07:47, James Masters wrote:
> I am rather amateur when it comes to OO methodology. If I don't use Loader
> to define my table classes, then it appears that I have to create a whole
> load of .pm files, one per table. Or if I do use Loader, then I have to
> create a di
Rose experts,
I am a newbie and trying to grasp fundamentals. My experience with
RoseDBObject has been much better than that with DBIC so far. I have got
Rose working under win32, MySQL using the Loader and am performing single
table queries successfully. Moving onto relationships, I seem to be
