put the transferfactory in the session scope, but that will take up a lot of memory if you have a lot of users
On Jan 13, 11:47 am, Andrew Bialecki <[email protected]> wrote: > Hey guys, > > New to Transfer, but been using CF for a long time. We're finally > beginning to think about using an ORM for sections of our application, > but we've got a somewhat unique situation. Essentially our > application allows users to select a datasource when they login and > then that datasource should be used for the duration of that users > session. Before I started experimenting with transfer, we literally > have the following structure for every cfquery: > > <cfquery name="something" datasource="#session.datasource#"> > SELECT name, address FROM users > </cfquery> > > so for each session, the same queries will be run, but against > different databases. > > I know Transfer only has knowledge of one datasource at a time, so is > there a way I can make this work? Sorry if this has been asked. I > found some tangential stuff about switch datasources at the thread > level, but I'm wondering if this is easier because it's at the session > level. > > Could I simply store the transferFactory object in session instead of > application scope and then set the datasource onSessionStart once I > know what it is?
-- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" 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/transfer-dev?hl=en
