I'm using MySQL 5.0.51a on Ubuntu Hardy Heron. As you say, this is a somewhat obscure bug. I guess the question is, do you want your product to work or not? You've acknowledged it's a valid problem. I tried to use Django 0.92 when it was the latest version and inspectdb fell over. I can't remember whether it was the same problem. Anyway, at the time I just lost interest and ignored Django for a year. So I'd gone to the trouble of installing the product, I'd bought and read the book, and when I went to use it it fell over on the very first thing I tried to do. That's a pretty good way to stop users from getting very far with your product. But hey, you develop your product how you like.
Yes, my fix was fragile. I didn't have the inclination to spend a lot of time fixing a product which until then had done nothing for me. I presume there are people who know a whole lot more about the code than I do who can maybe even log into the website. mysql> select column_name, referenced_table_name, referenced_column_name from information_schema.key_column_usage where table_name = 'expansions' and table_schema = DATABASE() and referenced_table_name is not null and referenced_column_name is not null; +-------------+-----------------------+------------------------+ | column_name | referenced_table_name | referenced_column_name | +-------------+-----------------------+------------------------+ | basegame | games | BGGID | | expansion | games | BGGID | +-------------+-----------------------+------------------------+ 2 rows in set (0.14 sec) --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
