I'm using Cayenne in a project where we have millions of rows
in most tables of the database, and my personal nightmare
is seeing how cayenne is disturbed by such things,
that should be kept on database side and never
should be part of an object-relational mapping framework
2007/6/21, Øyvind Harboe <oyvind.harbo..ylin.com>:
>
> On 6/21/07, Juergen Saar <juerge..saar.org> wrote:
> > Cayenne is a Framework that brings one of the best ORM available
> > and it would be foolish to implement such a horrible scenarium.
>
> I don't know what you find "horrible" about this scenario so I can't
> reply sensibly to your comment here.
>
> One of the really nice things about Cayenne is that it does allow
> adding code to handle screwed up databases on the application side.
>
> We're phasing out these screwed up database schemas and use of e.g.
> FoxPro/MSAccess, but the application needs to keep chugging along
> while we prepare to put it the old code/database schemas out its
> misery.
>
> > I think this special problem has to be solved by YOU
> > and not by the cayenne-team
>
> I don't know what I said to offend you. :-)
>
> I'm trying to ascertain whether this is something for which code
> hasn't been written yet and whether there would in fact be interest in
> a patch. It is not clear from the wiki page why this should never be
> done or attempted.
>
> Perhaps there is some recommended best practice to handle this case in
> the the application subclasses?
>
> The wiki page in question recommends implementing a query to
> implement the "getToXxx()" across databases, but that breaks when I
> want the "getToXxx()" to work for an uncommitted changed relationship
> across databases.
>
>
> --
> Øyvind Harboe
> http://www.zylin.com - eCos ARM & FPGA developer kit
>
This archive was generated by hypermail 2.0.0 : Thu Jun 21 2007 - 03:14:47 EDT