On 7/2/07, Jonas <[EMAIL PROTECTED]> wrote: > > With SAContext each model can live in a different database but when > you scale big there are all kinds of ways things might need to be > partitioned: > > * Some data gets accessed all the time while some other data is only > ever written. > > * You could want that certain records are in certain databases. E.g. > users 1 to 1,000,000 , or news/articles/information stored by year. > > * To use a separate database for each application that you mount > within the server. E.g. for a multi-blog application > > Would it be possible all that with SAContext?
I'll have to defer to Mike Bayer on this. BoundSessionStrategy may be able to do at least part of this, but the class was written by him and I don't really understand it. Mike, to improve the docstrings, who would use BoundSessionStrategy, the 'binds' argument, and the 'connectionbound' argument? Given that the 'binds' are fully defined before SAContext is instantiated, and the overall session engine is always the DEFAULT engine, is it possible to alter the engines chosen according to something in the current request (in Jonas's case, the current blog or the current record ID)? I thought that's what BoundSessionStrategy was for, but I don't see the mechanism for doing it. Or should one write a custom strategy for this? -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
