Hi Dermot!
On Saturday 28 Nov 2009 13:53:45 Dermot wrote:
> 2009/11/27 Steve Bertrand :
> > Dermot wrote:
> >> 2009/11/26 Scott Pham :
> >>> Have you looked at DBIx::Class?
> >>
> >> I'd 2nd that. DBIx is the way forward. You should be looking to stop
> >> writing SQL statements and moving towards
2009/11/27 Steve Bertrand :
> Dermot wrote:
>> 2009/11/26 Scott Pham :
>>> Have you looked at DBIx::Class?
>>>
>>
>> I'd 2nd that. DBIx is the way forward. You should be looking to stop
>> writing SQL statements and moving towards ORM. Try the example at
>> http://search.cpan.org/~frew/DBIx-Class-0
Dermot wrote:
> 2009/11/26 Scott Pham :
>> Have you looked at DBIx::Class?
>>
>
> I'd 2nd that. DBIx is the way forward. You should be looking to stop
> writing SQL statements and moving towards ORM. Try the example at
> http://search.cpan.org/~frew/DBIx-Class-0.08114/lib/DBIx/Class/Manual/Example
Dermot wrote:
> 2009/11/26 Scott Pham :
>> Have you looked at DBIx::Class?
>>
>
> I'd 2nd that. DBIx is the way forward. You should be looking to stop
> writing SQL statements and moving towards ORM. Try the example at
> http://search.cpan.org/~frew/DBIx-Class-0.08114/lib/DBIx/Class/Manual/Example
2009/11/26 Scott Pham :
> Have you looked at DBIx::Class?
>
I'd 2nd that. DBIx is the way forward. You should be looking to stop
writing SQL statements and moving towards ORM. Try the example at
http://search.cpan.org/~frew/DBIx-Class-0.08114/lib/DBIx/Class/Manual/Example.pod
Good luck,
Dp.
--
Have you looked at DBIx::Class?
Steve Bertrand wrote:
Hi everyone,
I'm looking to separate all of my MySQL logic (queries etc) out of my
projects methods and into it's own class.
Primarily, this is to provide me with the ability to change how the
back-end is interacted with, without having to