twistar icon indicating copy to clipboard operation
twistar copied to clipboard

Twistar is an object-relational mapper (ORM) for Python that uses the Twisted library to provide asynchronous DB interaction.

Results 11 twistar issues
Sort by recently updated
recently updated
newest added

Hi, as discussed in the issues #9, here's the final support for trasactions, along with tests and docs. Also in sync with current master branch. Hope all is ok!

As promised: Transactions which actually run in db threads. Supports fake nesting, SAVEPOINTs and can be used as context managers.

Currently twistar assumes that the primary key of a table is always called **id**. This of course not the case and twistar should provide an option to specify the primary...

feature request

Hi again, I'm pretty sure this is really not possible in the module: I have an app that works with two different databases (for various reasons), but obviously Twistar only...

feature request

Is it possible to load the model with its relationships directly ? something like `User.with('pictures')` to avoid a huge callback chain ? This example can be ok for one relationship,...

feature request

While working on [GlobaLeaks](https://github.com/globaleaks/GlobaLeaks) and evaluating twistar usage (https://github.com/globaleaks/GlobaLeaks/issues/1551) we are now evaluating the code quality of twistar in relation to python3. This ticket is to keep track of the...

Hi, In my code I sometimes have to go thought all objects of a certain type. By using the DBObject.all() function it seems all objects are instantiated in a large...

feature request

I'm thinking a way to implement a transaction handling to protect several operations, somethink like AR does: Account.transaction do balance.save! account.save! end (see http://api.rubyonrails.org/classes/ActiveRecord/Transactions/ClassMethods.html for other examples). this is very...

...to complement `deleteAll`. Updating stuff en-masse is inefficient right now.

feature request

(I will describe both the issue and the solution here because I already have a patch for this) After I added a call to `afterInit` in `DBObject.__init__`, it (now obviously)...