-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> since there seems no well-working fix, I now changed to postgresql. >> Now I built a django and a psycopg2 rpm for suse :) >> Maybe I'll release those to public, if they work good and if django >> keeps being nice to me :D >> > > Good to hear you found a way to avoid this problem getting > in you way. > > I'd suggest to reopen one of the tickets and put the information > to reproduce it there (it seems lak of such info lead to > the closing of these reports) so it isn't lost and gets a chance > of being taken in account by the core devs and/or people experienced > in MySQL. > > Regards, >
http://code.djangoproject.com/ticket/3424 I added a comment here. mfg Paul Rauch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iQIVAwUBRfwJbBG67lyyQrltAQIRkw//Xe7SzfeGIWegp135v1M24xxtKRXJnQsn hKQZIjxmGXk97Nz+A0ECJ9wMxfcRjeQ9uX/8Oj786aq0CUKeLsxqBeUyd43kEzpV GBNGVA34HHOq3n0iZOIkF2UgUO+1yWEpphkFAAo//nqCrvxoqPb093xWKF3HUwgr dP7gnbgfwZMgB6dWZe39EPHknjR4nmPWt7CyfLMu6jSMe0EGFtXiRw2l1FFDWulr kIQEkcnxDWI5XAIlD8CWnrIkRYWnl8WsNUl31NFJeU+GKCivLiAvnwzd9FJRGUbx ncRKs9Tz8VbEAYJzBzEoGz/X/tKgu1JqRQCCMrRZovLF+P17f+i7s9ttDcTXjCR+ BLGZ40h5V5Y3zRvBHtwdZl10D3QVFh45bgFvKvRNewF3OQov7V/rpHbT+NFHvS0N V8TkAxOxjb9N12zQ22HIJl7KF5B/53afHowz3/HR1zqRJTo9+vHz8wT1kgBINCtB KQU+YT3+0uwCtnu71J4SRPME5AIEEBofJmnHm6R95hkYN22BsWY7uoHxE2eUQXTc 8LpOcK5tizBy8fI+FVAKfOjgFp81DCwc6HXIhzdvnby/SerjWSjVUYXEu8LPWysg YVOmEP7WOkOmtcNzJZJmpbV4RWcuwxkMyMB+e2t0NQ3jLnAqLNZy24t3Ui1Pfaz2 UJXq54JezrU= =Dzm7 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
