I'm just starting to experiment with RDBO and like it very much so far.
Thanks, John and everybody!
I'm experimenting at work, where we use MySQL, with each instance
containing multiple databases. Via RDBO, I would like to use the same
DBI connection to query multiple databases, sometimes performi
hey Pal,
I did what you recommended below, and I wrote some stored procedures
to join the tables and get exactly what I want back. So far its
working out great!
I felt a little bit guilty posting my questions to the rose::db list.
I've joined some other database lists now so I'll try to sta
On Jan 18, 2007, at 11:57 PM, Neal Clark wrote:
> hey Pal,
>
> I did what you recommended below, and I wrote some stored procedures
> to join the tables and get exactly what I want back. So far its
> working out great!
>
> I felt a little bit guilty posting my questions to the rose::db list.
> I'
On 1/19/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> VIEWs are great, because they work out essentially as tables -- so
> you can create ROSE DB objects for selecting (though not inserting)
Sure you can do inserting. You can either do it with postgres
triggers, or you can probably even do it
On Jan 19, 2007, at 12:26 AM, Danial Pearce wrote:
> On 1/19/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
>> VIEWs are great, because they work out essentially as tables -- so
>> you can create ROSE DB objects for selecting (though not inserting)
>
> Sure you can do inserting. You can either d
On 1/19/07, Danial Pearce <[EMAIL PROTECTED]> wrote:
> On 1/19/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> > VIEWs are great, because they work out essentially as tables -- so
> > you can create ROSE DB objects for selecting (though not inserting)
>
> Sure you can do inserting. You can either
