Re: Problem with Django 1.5.1 and django-pyodbc
Hi, I had almost exactly the same issue just a week ago. Try using the django-pyodbc-azure fork. It works great for me. Mvg, Thomas De Reyck On 3-mei-2013, at 00:47, Kerry Calvert <kerryra...@gmail.com> wrote: > I have Django running on a Windows server with MS Sql using django-pyodbc. I > had Django version 1.4.2 working, and then upgraded to 1.5.1. This broke > django-pyodbc, which I fixed by updating to a fork by 'Gorah'. This got my > old site up and running. I then tried to create a new site, and when I ran > syncdb, the error is that get-grouping requires two arguments. This appears > to be a new requirement in django\db\models\sql\compiler.py, which is > imported by sql_server\pyodbc\compiler.py. I 'fixed' this by changing the > Django line to "def get_grouping(self, ordering_group_by=None):", but I > suspect that this is not the right thing to do. I'm an old programmer, but > new to Python, Django, and open source. Where should I go with this? > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Admin shows all users as staff and super user
Hi Siddharth, Thanks for your reply. I only create/delete/manage users via the admin itself, so there is no code to show you I guess. Furthermore, the auth table displays the correct values when queried directly. Kind regards, Thomas Op woensdag 1 mei 2013 10:48:10 UTC+2 schreef siddharth56660 het volgende: > > Hi Thomas, > > Can you paste the code snippet where you add the user in your auth table > (not the admin). > It might help in understanding the problem. > > -Siddharth > > > On Tue, Apr 30, 2013 at 11:45 PM, Thomas De Reyck < > thomas%d...@gtempaccount.com > wrote: > >> Hi everyone, >> >> My very first question here. I hope anyone can help me out with this... >> >> I have created a Django powered site for my company. Everything works >> perfectly, except in our production environment, >> where I have one bug in the admin that is quite annoying: >> >> When I click a user to edit it, the "Staff" and "SuperUser" checkboxes >> are always checked for every user, even when they >> shouldn't be. The database however does record these properties properly, >> and they work correctly in the application. Only >> the admin is displaying them incorrectly in the "edit" page for a user. >> When looking at the user overview in the admin, the >> "staff" property is correctly displayed. >> >> Because of this error we need to be extra cautious when editing users, >> because we don't accidentally want to make anyone >> a staff or superuser. >> >> Does anyone know how I can attempt to debug this? Where should I start? >> >> I am running: >> Django 1.5.1 on Ubuntu 12.04 with SQL Server 2008R2 as my database (via >> pyodbc->UnixODBC->FreeTDS). >> >> Thanks in advance for any hints you can provide! >> >> Kind regards, >> Thomas >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com . >> To post to this group, send email to django...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/django-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Admin shows all users as staff and super user
Hi everyone, My very first question here. I hope anyone can help me out with this... I have created a Django powered site for my company. Everything works perfectly, except in our production environment, where I have one bug in the admin that is quite annoying: When I click a user to edit it, the "Staff" and "SuperUser" checkboxes are always checked for every user, even when they shouldn't be. The database however does record these properties properly, and they work correctly in the application. Only the admin is displaying them incorrectly in the "edit" page for a user. When looking at the user overview in the admin, the "staff" property is correctly displayed. Because of this error we need to be extra cautious when editing users, because we don't accidentally want to make anyone a staff or superuser. Does anyone know how I can attempt to debug this? Where should I start? I am running: Django 1.5.1 on Ubuntu 12.04 with SQL Server 2008R2 as my database (via pyodbc->UnixODBC->FreeTDS). Thanks in advance for any hints you can provide! Kind regards, Thomas -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
