Michael,
Check this thread:
http://www.mail-archive.com/rose-db-object@lists.sourceforge.net/msg00260.html
I hope that helps
2007/6/20, Michael Reece <[EMAIL PROTECTED]>:
>
> i am looking to freeze/thaw (or yaml, doesn't really matter..)
> unblessed data structures into a mysql column.
>
> has a
Is it possible to have separate read and write database connections in
Rose::DB::Object?
For example, I might have read to:
read.db.com
...and...write to:
write.db.com
...is it possible to get any updates/deletes and inserts (and other
things that change the DB) to write.db.com but have
John Siracusa wrote:
> On 6/19/07 9:59 PM, mla wrote:
>> Cool. Can I help? Do you already have a general approach in mind?
>
> The first step is to make a decent SQL abstract abstraction made up of
> mutable objects which link back to the relevant bits of RDBO metadata. I'll
> probably validate t
On 6/19/07 9:59 PM, mla wrote:
> Cool. Can I help? Do you already have a general approach in mind?
The first step is to make a decent SQL abstract abstraction made up of
mutable objects which link back to the relevant bits of RDBO metadata. I'll
probably validate that piece by re-implementing the
John Siracusa wrote:
> On 6/19/07, mla <[EMAIL PROTECTED]> wrote:
>> The features I'm interested in are:
>>
>>o Providing a somewhat consistent interface between these ad-hoc
>> result sets and normal RDBO objects.
>>
>>o Catching field typos which the accessors/mutators would give you
i am looking to freeze/thaw (or yaml, doesn't really matter..)
unblessed data structures into a mysql column.
has anyone already written a Column class that handles this
transparently?
---
michael reece :: software engineer :: [EMAIL PROTECTED]
On 6/18/07, mla <[EMAIL PROTECTED]> wrote:
> Subselect?
>
> SELECT count(*)
>FROM (
> SELECT DISTINCT a_id, b_id
>FROM a_b_map
> WHERE a_id = xxx
>) s
So far, that looks like the best option to me. Can anyone think of
anything better?
-John
---
On 6/19/07, mla <[EMAIL PROTECTED]> wrote:
> The features I'm interested in are:
>
>o Providing a somewhat consistent interface between these ad-hoc
> result sets and normal RDBO objects.
>
>o Catching field typos which the accessors/mutators would give you.
> (although you could
