Re: one model, multiple database instances

Mario Ruggier wrote:
[...]
> Another situation in which this could apply is for migrating from one
> db+model to another... a little modeling mapping code could read from
> one EC and populate another that uses a modified model. This may not 
> be the most efficient to way to do this, but possibly the most 
> flexible and one that would guarantee data integrity and consistency 
> the most. Any opinions on whether this would be a good idea or not?

I'm sure we've played with that idea some day in the past, if I remember well it
was probably with Yannick Gingras (I can't check the archives right now).

  The problem is that, while this sounds interesting, this could
  probably only be done with small databases --because, unless we
  want to automatically analyse a model in detail, handling
  relationships will end up in loading a whole database in memory.

Moreover, I'm convinced that it will be difficult to cover every
transformations. But I can be proved wrong!

-- Sébastien.



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285