On Fri, 21 Dec 2007 16:11:08 -0800 Darren Duncan <[EMAIL PROTECTED]> wrote:
DD> At 6:20 PM -0500 12/21/07, John Siracusa wrote:
>> On 12/21/07 3:43 PM, Ted Zlatanov wrote:
>>> I've set up all the right things in a Rose::DB class to support this.
>>> Now I find myself with the need for four class
At 6:20 PM -0500 12/21/07, John Siracusa wrote:
>On 12/21/07 3:43 PM, Ted Zlatanov wrote:
>> I've set up all the right things in a Rose::DB class to support this.
>> Now I find myself with the need for four class hierarchies to handle
>> slightly different things in those four environments. Ins
On 12/21/07 3:43 PM, Ted Zlatanov wrote:
> I've set up all the right things in a Rose::DB class to support this.
> Now I find myself with the need for four class hierarchies to handle
> slightly different things in those four environments. Instead, I'm
> wondering if I can have:
>
> DB/auto/prod/
Let's say I have two DB domains: prod/dev and two DB types: a/b. All
four combinations have 99% of the same data structure but need different
login info and some slightly different fields (e.g. the table 'cats' in
dev-a has an extra timestamp column).
I've set up all the right things in a Rose::D
