Code

Changes between Initial Version and Version 1 of Ticket #10164, comment 26


Ignore:
Timestamp:
03/15/13 11:49:07 (13 months ago)
Author:
lukeplant
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10164, comment 26

    initial v1  
    33This bug is accepted - the current behaviour is regarded as a bug, and we will accept good patches fixing this problem. The limitation is someone willing to write a good patch. You can see my comments on the previous patch above. 
    44 
    5 However, I should say that you really should consider a better database for production. Even for development, differences between development and production can really bite. Because of this, all experienced Django developers only use SQLite as a toy, strictly for throw away database, and none of us are likely to write a patch for this. 
     5However, I should say that you really should consider a better database for production. Even for development, differences between development and production can really bite. Because of this, all experienced Django developers only use SQLite as a toy, strictly for quick throw-away databases and experiments, and so none of us are likely to write a patch for this. 
    66 
    7 But patches welcome! 
     7But patches are welcome!