I know, but the original system (in asp 3) and i try to migration to .net with monorail, ar ... and this particular (and bizzar) behavor is a customer requires. :(
so any idea? josh robb wrote: > On Thu, Dec 4, 2008 at 6:06 AM, Gabriel Mancini de Campos > <[EMAIL PROTECTED]> wrote: > > > > hi i have thinking... > > > > is not a better choice create a public class MultiBaseInterceptior : > > IInterceptor ??? > > and in moment of persistence, change the DB? > > someone here, know's which method from IInterceptor will be the better > > to implement the change??? > > This sounds like a pretty insane idea to me. > > Basically - you've done all your logic/validation using one DB and > then you want to write the actual changes to another. > > I guess if you want all your reads to happen from one DB and all your > writes to happen to another - then it's possible this isn't bad idea. > > Generally - you're going to get FK constraint errors, duplicate keys > and all sorts of problems if you go this path (and it's not exactly > what you want). > > j. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
