I'm thinking of having a demo user that is "live" for a particular app that allows users to edit data. Rather than have a separate demo system I'd like to run the demo user on the same live app that normal users use. Problem is I want to wipe and rebuild a stock set of data for this user nightly so as to have a clean slate each day for demo users to start with.
What I thought would make sense is to have any user's datasource for app data be a field in the main login table. So, one login datasource for all users and then a 2nd data source for user app data. That way the demo user could be on a data source by themselves and I could do whatever to its data each night without abusing the data source normal users are on. Right now I do as the demos I've seen for MG. The model cfcs init with a dsn and that is then used in each function as "variables.dsn". Wondering what the best method might be to do the above. Just store as a session var? Wanted to see if anyone doing anything like this or had a suggestion. Thank you! -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
