Thanks for all these helpful feedback.
If I still want to use SQLite, and I still need to do vertical partition,
what can I do? Am I out of luck?
On Friday, August 14, 2015 at 2:04:37 AM UTC-7, Jinghui Niu wrote:
I have three different DBs, one is person.db, another is journal.db, yet
Thank you very much Jonathan for your very intuitive analogy!
Basically I just want to put people, journal and tag tables(each will
potentially be very large) into different DBs, if I write that logic, how
can I integrate it with SQLAlchemy? Could you give me a rough idea here? Or
point some
On Friday, August 14, 2015 at 5:16:48 PM UTC-4, Jinghui Niu wrote:
If I still want to use SQLite, and I still need to do vertical partition,
what can I do? Am I out of luck?
You can, but not with a two-phase commit.
Two-phase commit basically works like this:
- round 1, everyone
Thanks Jonathan for pointing out the direction, it is very helpful to know
where I can find more info.
On Friday, August 14, 2015 at 5:06:09 PM UTC-7, Jonathan Vanasco wrote:
Well, this problem doesn't really have anything to do with SqlAlchemy --
you should probably ask people for advice on
Well, this problem doesn't really have anything to do with SqlAlchemy --
you should probably ask people for advice on the Sqlite lists or Stack
Overflow.
You can segment out your database into 3 files using the example above.
You will just run into an issue where -- because there isn't a
Just a thought, if I don't commit those three tables together in my
application, can I just use 3 Session objects to commit them separately,
without having to worry about this two phase issue? I want to go simple,
not sure if I can handle this fancy stuff:)
On Friday, August 14, 2015 at
