Re: I would like to report a bug but I can't log in
Well, I think we can all see where you get your nickname. On Jan 4, 12:03 am, Friendless wrote: > On Jan 4, 2:42 pm, "Karen Tracey" wrote: > > > I'll admit your tone here is starting to make me lose interest in your > > problem report. > > Admit it, you weren't very interested in the first place. You've given > me all sorts of reasons as to why the bug shouldn't be fixed, despite > (a) evidence that it is a bug, and (b) at least a clue as to how to > fix it. The simple fact of the matter is that Django failed on the > very first thing I did with it, your website doesn't work (yes, I did > try logging in using the link as Ramiro suggested), and my first > encounter with the community has been hostile. Django's doing nothing > for me, and I refuse to get involved with a community that won't even > believe me, let alone help. I've given you a good bug report, but now > I'm out of here. Do whatever you like. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: I would like to report a bug but I can't log in
On Sat, 2009-01-03 at 22:03 -0800, Friendless wrote: > On Jan 4, 2:42 pm, "Karen Tracey" wrote: > > I'll admit your tone here is starting to make me lose interest in your > > problem report. > > Admit it, you weren't very interested in the first place. You've given > me all sorts of reasons as to why the bug shouldn't be fixed, despite Wow. That's just unbelievably rude. If somebody isn't interested in helping you, they won't reply to the original mail, not spend a few thousand words and four responses trying to help work out what is going on and untold hours trying to repeat the problem. If you don't like using Django, that's fine, but having followed this thread, I can say that you are leaping to some fairly large and unjustified conclusions and being very unfair to Karen and Ramiros' efforts. Please grow some manners. Malcolm --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: I would like to report a bug but I can't log in
On Sun, Jan 4, 2009 at 1:03 AM, Friendless wrote: > > On Jan 4, 2:42 pm, "Karen Tracey" wrote: > > I'll admit your tone here is starting to make me lose interest in your > > problem report. > > Admit it, you weren't very interested in the first place. You've given > me all sorts of reasons as to why the bug shouldn't be fixed, despite > (a) evidence that it is a bug, and (b) at least a clue as to how to > fix it. The simple fact of the matter is that Django failed on the > very first thing I did with it, your website doesn't work (yes, I did > try logging in using the link as Ramiro suggested), and my first > encounter with the community has been hostile. Django's doing nothing > for me, and I refuse to get involved with a community that won't even > believe me, let alone help. I've given you a good bug report, but now > I'm out of here. Do whatever you like. > If I had no interest in fixing the bug I would not have responded nor tried to recreate it on two different machines (installing a new version of MySQL on one of them to do so). I simply stated that it isn't high enough priority for me to pursue any further at this point given my knowledge of the code, what I feel are the numbers of people that might hit this problem, and and the fact that I cannot recreate it. I am sorry if you feel that was hostile. I'm sorry Django doesn't fit your needs and good luck with whatever software you choose to use instead. Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: I would like to report a bug but I can't log in
On Jan 4, 2:42 pm, "Karen Tracey" wrote: > I'll admit your tone here is starting to make me lose interest in your > problem report. Admit it, you weren't very interested in the first place. You've given me all sorts of reasons as to why the bug shouldn't be fixed, despite (a) evidence that it is a bug, and (b) at least a clue as to how to fix it. The simple fact of the matter is that Django failed on the very first thing I did with it, your website doesn't work (yes, I did try logging in using the link as Ramiro suggested), and my first encounter with the community has been hostile. Django's doing nothing for me, and I refuse to get involved with a community that won't even believe me, let alone help. I've given you a good bug report, but now I'm out of here. Do whatever you like. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: I would like to report a bug but I can't log in
On Sat, Jan 3, 2009 at 4:43 PM, Friendless wrote: > I'm using MySQL 5.0.51a on Ubuntu Hardy Heron. > Hmm, that looks later than what I tested on (5.0.45). I'm not wanting to mess with the install I have on Ubuntu, so I installed the latest 5.0.67 community version on a test machine (which happens to be a Windows box) and I still can't recreate what you see: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.0.67-community-nt MySQL Community Edition (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> CREATE TABLE `games` ( -> `bggid` int(10) unsigned NOT NULL, -> `name` varchar(256) NOT NULL default '', [snipped all the others] -> PRIMARY KEY (`bggid`) -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Query OK, 0 rows affected (0.32 sec) mysql> CREATE TABLE `expansions` ( -> `basegame` int(10) unsigned NOT NULL, -> `expansion` int(10) unsigned NOT NULL, -> KEY `expansions_basegame` (`basegame`), -> KEY `expansions_expansion` (`expansion`), -> CONSTRAINT `expansions_basegame` FOREIGN KEY (`basegame`) REFERENCES -> `games` (`BGGID`), -> CONSTRAINT `expansions_expansion` FOREIGN KEY (`expansion`) -> REFERENCES `games` (`BGGID`) -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Query OK, 0 rows affected (0.27 sec) 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 (10.40 sec) > 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'll admit your tone here is starting to make me lose interest in your problem report. But, perhaps I am misinterpreting your tone, and I do in fact like to help fix Django bugs, which this seems to be, so I'll just say: Django is not "my product". None of the $0.00 you paid for Django found its way into my pocket. I'm a contributor, one among many. That doesn't make Django "mine". Nor does one bug remove Django from the class of software that "works". There would be precious little software you could call "working" if that was the case. > 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. > You seem to be missing the fact that Django is nobody's product but rather an open source project. Community members contribute according to their own interests, abilities, and availability. You've apparently hit a bug, due it seems to your database having characteristics not considered by whoever wrote inspectdb. That's unfortunate. You've reported it -- thanks for that. Please realize, though, that in an all-volunteer community getting an obscure bug that you happen to care about fixed may require more from you than simply reporting the problem, posting a fix that happened to work for your specific case, and threatening that failure to fix the bug will scare away untold numbers of new users. > > 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. > Sorry, but I don't happen to be someone who knows any more about that code than you do, and I cannot recreate the problem. So developing a more robust fix is not going to be high on my priority list. Since you can recreate it, it might be good for Django and helpful to the next person who happens to start out with a similarly configured DB if you chose to make the effort to develop and post a more robust fix, but that's entirely up to you. On the login, Ramiro has responded with something he encountered on a new login that may help you get past what you are seeing. There is also the settings page option: http://code.djangoproject.com/settings that I mentioned a couple of times with no feedback from you as to whether
Re: I would like to report a bug but I can't log in
On Fri, Jan 2, 2009 at 8:03 AM, Friendless wrote: > > I tried to report a bug anonymously and got told I was spam, so I > signed up, got the email, activated the account, and still can't log > in and still can't report the bug. I've been using Django 30 minutes > and I'm already frustrated! I've just took 15 seconds and followed the same process creating a test user and I can login perfectly to the code.djangoproject.com site. Something slightly weird: after activating the account, I followed the link to login for the first time, once I entered the user name and password I got redirected to the djangoproject.com site and going back to code.djangoproject still didn't show me as logged in. So I had to log in again using the 'Login' link located at the upper right corner of the page (in the light green strip), that worked right away. Regards, -- Ramiro Morales --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: I would like to report a bug but I can't log in
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 -~--~~~~--~~--~--~---
Re: I would like to report a bug but I can't log in
On Fri, Jan 2, 2009 at 9:46 PM, Friendless wrote: > > I still can't log in. Sometimes I get a dialogue box, sometimes a > form, but it just never works. My username is Friendless. Did you try just filling in some settings at the page I pointed to in the earlier mail? That method doesn't require login. Sorry, I can't help with the login not working, I don't have (nor want) any ability to do anything with trac logins. You are the first person I recall ever reporting a problem with one, though. Anyway, as I > have your permission to post my bug here, I'll do so. I have a legacy > MySQL database to which I'm adding access using Django. I wrote the > create scripts for this db by hand while I was learning MySQL so > they're "quirky". I ran inspectdb and it failed like this: > > Traceback (most recent call last): > [snipped] File "/usr/lib/python2.5/site-packages/django/db/backends/mysql/ > introspection.py", line 80, in get_relations >other_field_index = self._name_to_index(cursor, other_table) > [other_field] > KeyError: u'BGGID' > > i.e. it can't find the column that I have a foreign key constraint on. > The tables in question are: > > CREATE TABLE `expansions` ( > `basegame` int(10) unsigned NOT NULL, > `expansion` int(10) unsigned NOT NULL, > KEY `expansions_basegame` (`basegame`), > KEY `expansions_expansion` (`expansion`), > CONSTRAINT `expansions_basegame` FOREIGN KEY (`basegame`) REFERENCES > `games` (`BGGID`), > CONSTRAINT `expansions_expansion` FOREIGN KEY (`expansion`) > REFERENCES `games` (`BGGID`) > ) ENGINE=InnoDB DEFAULT CHARSET=utf8 > > CREATE TABLE `games` ( > `bggid` int(10) unsigned NOT NULL, > `name` varchar(256) NOT NULL default '', > `average` float default '0', > `rank` int(11) default '-1', > `yearPublished` int(11) default '0', > `minPlayers` int(10) unsigned default '0', > `maxPlayers` int(10) unsigned default '0', > `playTime` int(10) unsigned default '0', > `usersRated` int(10) unsigned default '0', > `usersTrading` int(10) unsigned default '0', > `usersWanting` int(10) unsigned default '0', > `usersWishing` int(10) unsigned default '0', > `averageWeight` float default '0', > `bayesAverage` float default '0', > `stdDev` float default '0', > `median` float default '0', > `numComments` int(10) unsigned default '0', > `expansion` int(10) unsigned NOT NULL default '0', > `thumbnail` varchar(256) default '', > `usersOwned` int(10) unsigned default '0', > PRIMARY KEY (`bggid`) > ) ENGINE=InnoDB DEFAULT CHARSET=utf8 > > Note that in the first table the column name is BGGID and in the > second it's bggid. I always presumed this worked as MySQL doesn't > complain, and I hope it would if I defined a constraint that made no > sense. (Well, yes, one would hope that...whether you can really count on it, I don't know.) You certainly picked an odd one to trip over in your first 30 minutes of using Django. What version of MySQL are you using? I cannot recreate this behavior with: Server version: 5.0.45-Debian_1ubuntu3.4-log Debian etch distribution If I cut and paste your create table statements into a mysql command session (with one specifying all uppercase BGGID and one all lowercase), a subsequent inspectdb runs fine. Inspecing the output of the command Django uses to query the DB: 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.00 sec) shows mysql is returning all-lowercase even though the create table I used specified it as all-uppercase. So I am wondering if the behavior you see is a bug they have fixed, perhaps? > Anyway, I hacked the code in introspection.py. I changed line > 80 to this: > > other_field_index = self._name_to_index(cursor, other_table) > [other_field.lower()] > > i.e. I just added the .lower(), and it works for me, and then > inspectdb worked fine. That fix seems a bit fragile. I wonder what would happen if you specified all-uppercase BGGD in the games table and all-lowercase in the expansions table what behavior you would see and if instead of .lower() here you would need an .upper() to make things work? > Anyway, the problem is that inspectdb fails due > to case quirks, and with a completely unhelpful error message. It > would be so much nicer if it either figured out for itself (which it > should do if the case difference is a valid thing to do), or else give
Re: I would like to report a bug but I can't log in
I still can't log in. Sometimes I get a dialogue box, sometimes a form, but it just never works. My username is Friendless. Anyway, as I have your permission to post my bug here, I'll do so. I have a legacy MySQL database to which I'm adding access using Django. I wrote the create scripts for this db by hand while I was learning MySQL so they're "quirky". I ran inspectdb and it failed like this: Traceback (most recent call last): File "manage.py", line 11, in execute_manager(settings) File "/usr/lib/python2.5/site-packages/django/core/management/ __init__.py", line 340, in execute_manager utility.execute() File "/usr/lib/python2.5/site-packages/django/core/management/ __init__.py", line 295, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.5/site-packages/django/core/management/ base.py", line 192, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.5/site-packages/django/core/management/ base.py", line 219, in execute output = self.handle(*args, **options) File "/usr/lib/python2.5/site-packages/django/core/management/ base.py", line 348, in handle return self.handle_noargs(**options) File "/usr/lib/python2.5/site-packages/django/core/management/ commands/inspectdb.py", line 10, in handle_noargs for line in self.handle_inspection(): File "/usr/lib/python2.5/site-packages/django/core/management/ commands/inspectdb.py", line 36, in handle_inspection relations = connection.introspection.get_relations(cursor, table_name) File "/usr/lib/python2.5/site-packages/django/db/backends/mysql/ introspection.py", line 80, in get_relations other_field_index = self._name_to_index(cursor, other_table) [other_field] KeyError: u'BGGID' i.e. it can't find the column that I have a foreign key constraint on. The tables in question are: CREATE TABLE `expansions` ( `basegame` int(10) unsigned NOT NULL, `expansion` int(10) unsigned NOT NULL, KEY `expansions_basegame` (`basegame`), KEY `expansions_expansion` (`expansion`), CONSTRAINT `expansions_basegame` FOREIGN KEY (`basegame`) REFERENCES `games` (`BGGID`), CONSTRAINT `expansions_expansion` FOREIGN KEY (`expansion`) REFERENCES `games` (`BGGID`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 CREATE TABLE `games` ( `bggid` int(10) unsigned NOT NULL, `name` varchar(256) NOT NULL default '', `average` float default '0', `rank` int(11) default '-1', `yearPublished` int(11) default '0', `minPlayers` int(10) unsigned default '0', `maxPlayers` int(10) unsigned default '0', `playTime` int(10) unsigned default '0', `usersRated` int(10) unsigned default '0', `usersTrading` int(10) unsigned default '0', `usersWanting` int(10) unsigned default '0', `usersWishing` int(10) unsigned default '0', `averageWeight` float default '0', `bayesAverage` float default '0', `stdDev` float default '0', `median` float default '0', `numComments` int(10) unsigned default '0', `expansion` int(10) unsigned NOT NULL default '0', `thumbnail` varchar(256) default '', `usersOwned` int(10) unsigned default '0', PRIMARY KEY (`bggid`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 Note that in the first table the column name is BGGID and in the second it's bggid. I always presumed this worked as MySQL doesn't complain, and I hope it would if I defined a constraint that made no sense. Anyway, I hacked the code in introspection.py. I changed line 80 to this: other_field_index = self._name_to_index(cursor, other_table) [other_field.lower()] i.e. I just added the .lower(), and it works for me, and then inspectdb worked fine. Anyway, the problem is that inspectdb fails due to case quirks, and with a completely unhelpful error message. It would be so much nicer if it either figured out for itself (which it should do if the case difference is a valid thing to do), or else give a better error message. Anyway, after sorting that out I went on to try to access a table with no primary key, and discovered that didn't work either :-). I also managed to hack around that. Despite the problems I'm really enjoying Django and think I will keep using it. John On Jan 3, 12:04 am, "Karen Tracey" wrote: > On Fri, Jan 2, 2009 at 5:03 AM, Friendless > wrote: > > > > > I tried to report a bug anonymously and got told I was spam, so I > > signed up, got the email, activated the account, and still can't log > > in and still can't report the bug. I've been using Django 30 minutes > > and I'm already frustrated! > > This is the first report I've ever seen of trouble with logging in after > creating an account, so I'm not sure what's wrong there. An alternative way > to avoid the spam blocker is to just fill in some settings here: > > http://code.djangoproject.com/settings > > If you've only been using Django for 30 minutes, though, it might be more > useful to post your problem here. 30 minutes in you are far more likely to > be hitting user misunderstandings than genuine bugs
Re: I would like to report a bug but I can't log in
On Fri, Jan 2, 2009 at 5:03 AM, Friendless wrote: > > I tried to report a bug anonymously and got told I was spam, so I > signed up, got the email, activated the account, and still can't log > in and still can't report the bug. I've been using Django 30 minutes > and I'm already frustrated! > > This is the first report I've ever seen of trouble with logging in after creating an account, so I'm not sure what's wrong there. An alternative way to avoid the spam blocker is to just fill in some settings here: http://code.djangoproject.com/settings If you've only been using Django for 30 minutes, though, it might be more useful to post your problem here. 30 minutes in you are far more likely to be hitting user misunderstandings than genuine bugs, and the list is a much better place for help with those. Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
I would like to report a bug but I can't log in
I tried to report a bug anonymously and got told I was spam, so I signed up, got the email, activated the account, and still can't log in and still can't report the bug. I've been using Django 30 minutes and I'm already frustrated! --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
