Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-26 Thread Clint Ecker
On 4/25/06, Ken Kennedy <[EMAIL PROTECTED]> wrote:
I'd say put 'em there!Done---Clint Ecker[EMAIL PROTECTED]http://phaedo.cx

--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---


Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-26 Thread Clint Ecker
There was already a bug report on this, and a simple patch:http://code.djangoproject.com/ticket/1677On 4/26/06, 
Rudolph <[EMAIL PROTECTED]> wrote:
This revision also causes another minor bug. When running syncdb ittells youAdding permission ''for every permission. This is caused by the __repr__ and __str__changes. Shall I file a bug report?
Clint Ecker[EMAIL PROTECTED]http://phaedo.cx

--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---


Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-26 Thread Rudolph

This revision also causes another minor bug. When running syncdb it
tells you
Adding permission ''
for every permission. This is caused by the __repr__ and __str__
changes. Shall I file a bug report?


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-25 Thread Ken Kennedy

I'd say put 'em there!


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-25 Thread Clint Ecker
On 4/25/06, Rudolph <[EMAIL PROTECTED]> wrote:
The above fixes the issue, but to completely remove all uppercasednames also do:BEGIN;UPDATE django_content_type set name='group' where model='group';UPDATE django_content_type set name='user' where model='user';
COMMIT;Thanks for putting those together, now I'm trying to figured out where the best place to put this information is?

Is this a good place? http://code.djangoproject.com/wiki/RemovingTheMagic#Databasechangesyoullneedtomake

Or does that only deal with changes from 0.9.1 to 0.91MR? ---Clint Ecker[EMAIL PROTECTED]http://phaedo.cx

--~--~-~--~~~---~--~~
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  -~--~~~~--~~--~--~---


Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-25 Thread Rudolph

The above fixes the issue, but to completely remove all uppercased
names also do:

BEGIN;
UPDATE django_content_type set name='group' where model='group';
UPDATE django_content_type set name='user' where model='user';
COMMIT;


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-25 Thread Rudolph

Fix this in PostgreSQL like this:

BEGIN;
UPDATE auth_permission set name='Can add group' where
codename='add_group';
UPDATE auth_permission set name='Can change group' where
codename='change_group';
UPDATE auth_permission set name='Can delete group' where
codename='delete_group';
UPDATE auth_permission set name='Can add user' where
codename='add_user';
UPDATE auth_permission set name='Can change user' where
codename='change_user';
UPDATE auth_permission set name='Can delete user' where
codename='delete_user';
COMMIT;


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



Re: MR: Revision 2745 and up -- Syncdb breakage, and why

2006-04-25 Thread Rudolph

This should be on the Magic Removal wiki page, including SQL commands
to update the records. I'll create the PostgreSQL commands within a few
hours and post them here.


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---