On 12/02/2015 10:18 AM, Jonathan Vanasco wrote: > > I recently had to "split" or partition another table into 2 -- one of high > write and low write access. The new table is just the high-write columns > fkey'd onto the original table, and handled with a relationship. > > I was wondering if there was any "shortcut" in sqlalchemy to automatically > handle stuff like this, or a common pattern. > > The best I could think of is using an association proxy to map the columns > back -- but that must be done for every column, and doesn't handle the > creation of the new table as a dependency. > > My current manual solution works, just wondering if there are better ways. >
if this is postgresql, I'd just put INHERITS on the PG side and be done with it, since it's only the writes you want to split out. otherwise, one-to-one is more or less joined table inheritance. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
