On 2007-10-11 17:10:30 -0600, jf <[EMAIL PROTECTED]> said: > > Hi all, I am currently using Django on a project with a database of > fairly large table sizes, and I have encountered a strange and > potentially dangerous bug, of which I am not sure the cause. This is > not really a bug report, as I haven't really had the time necessary to > gather enough information to file an official bug report, but I would > like to get some more expert opinions on the matter if I could. > > Here goes: Using Django, I am inserting rather large amounts of > records into an sqlite3 database on OS X v10.4.10. I have yet to > perfect my Django development cycle, and so I spend a decent amount of > time changing around models and recreating databases as I develop. At > one point, after spending hours writing to the database, the python > process had finished, however the database still appeared to be empty, > except for the fact that the filesystem thought its size was ~53Mb. > Not having time to investigate further, I deleted the database and > decided to try again later. For a separate part of the project, I > wanted to install matplotlib and pylab, and so I moved on to do this > next instead. However, compilation errors abounded when I did so, > namely that there were odd characters in my system and various other > header files. When I looked at these files, they indeed appeared to > binary, except for the fact that there were visible strings of ASCII > text, which clearly came from the data I had been trying to insert > into the database (strangely enough these were actually DNA sequences, > but not from a virus). > > I was able to restore the headers that I needed in order to compile, > however, I have no idea what else on my system may have been touched > by this. Days later I had a problem with import site every time I > would start up python, and found another string of DNA had inserted > itself into my Numeric.pth file. The difficulties so far have been > easy enough to fix, but this is such a strange, and potentially > dangerous problem, that I am cautious about writing to the database > any further until I have identified its cause. I understand that this > is likely a sqlite issue, but if anyone has any further insight it > would be greatly appreciated. > > Thanks! > Jared > > > Hey Jared,
Questions of this nature should be directed to django-users and/or one of the other projects as it sounds like your issue isn't 100% Django. django-dev is reserved for the development of Django itself. -- Brian Rosner --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
