Changes between Initial Version and Version 1 of Ticket #15507, comment 3


Ignore:
Timestamp:
02/26/11 18:00:08 (4 years ago)
Author:
russellm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15507, comment 3

    initial v1  
    44> We shouldn't worry about savepoints only being available for InnoDB as we don't even turn off COMMIT/ROLLBACK calls when doing queries against MyISAM tables. Besides, we can't detect "for InnoDB" it on the database connection level as it's a property of the table.
    55
    6 Granted -- I just want to make sure that it's truly a no-op. MySQL MyISAM ignores transactions, and other than not having transactional behavior, it doesn't affect Django's internals. However, some of Django's internals use savepoints (get_or_create, for instance), so we need to make sure adding this behavior doesn't have other consequences on databases that don't support it.
     6Granted -- I just want to make sure that it is truly a no-op. MySQL MyISAM ignores transactions, and other than not having transactional behavior, it doesn't affect Django's internals. However, some of Django's internals use savepoints (get_or_create, for instance), so we need to make sure adding this behavior doesn't have other consequences on databases that don't support it.
Back to Top