Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
-+-
 Reporter:  Maxim Syabro |Owner:  nobody
   |   Status:  closed
 Type:  Bug  |  Version:  1.0
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  inspectdb|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 MySQL's behavior with regard to case-sensitivity was discussed thoroughly
 in #16592, and one of the most knowledgeable contributors on MySQL support
 reached this conclusion:

 > I think the problematic behavior is due to the bugs and inconsistencies
 of MySQL. I don't think there is a straightforward solution to this that
 doesn't involve a lot of weird hacking around and exceptions.

 Trying to fix things in Django would be very complicated and is likely to
 make things worse. I totally agree with Karen's conclusion in the first
 comment.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
-+-
   Reporter:  Maxim  |  Owner:  nobody
  Syabro   | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.0|   Severity:  Normal
 Resolution: |   Keywords:  inspectdb
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by ramiro):

 * keywords:   => inspectdb
 * ui_ux:   => 0
 * easy:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by syabro):

 Replying to [comment:3 aatif]:
 > How can I check both of these? i-e '''lower_case_table_names''' and
 '''create ... if not exists'''.
 By query "SHOW variables like 'lower_case_table_names'"

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by aatif):

 How can I check both of these? i-e '''lower_case_table_names''' and
 '''create ... if not exists'''.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Old description:

> I have an application with name localModels and lower_case_table_names
> mysql variable=1, which said to MySQL automatically convert table name to
> lowercase.
> Let's look in djnago.core.management.commnads.syncdb.py, line 67:
> {{{
> #!python
> if connection.introspection.table_name_converter(model._meta.db_table) in
> tables:
> continue
> }}}
> connection.introspection.table_name_converter(model._meta.db_table) =
> 'localModels_tablename'
> in tables we have
> (..., 'localmodels_tablename', ...)
> so here your condition doesn't work, beacuse
> 'localModels_tablename'!='localmodels_tablename'.
> And we have an exception in manage.py syncdb:
> _mysql_exceptions.OperationalError: (1050, "Table 'localmodels_tablename'
> already exists")
>
> So I see at least 2 ways:
> 1. Generate SQL 'CREATE TABLE `tablename` IF NOT EXIST'
> 2. Check MySQL's lower_case_table_names variable and change condition on
> line 67.

New description:

 I have an application with name `localModels` and `lower_case_table_names`
 mysql variable=1, which said to MySQL automatically convert table name to
 lowercase.
 Let's look in `djnago.core.management.commnads.syncdb.py`, line 67:
 {{{
 #!python
 if connection.introspection.table_name_converter(model._meta.db_table) in
 tables:
 continue
 }}}
 `connection.introspection.table_name_converter(model._meta.db_table) =
 'localModels_tablename'`
 in tables we have
 `(..., 'localmodels_tablename', ...)`
 so here your condition doesn't work, beacuse
 `'localModels_tablename'!='localmodels_tablename'`.
 And we have an exception in `manage.py syncdb`:
 {{{
 _mysql_exceptions.OperationalError: (1050, "Table 'localmodels_tablename'
 already exists")
 }}}

 So I see at least 2 ways:

  1. Generate SQL {{{'CREATE TABLE `tablename` IF NOT EXIST'}}}
  2. Check MySQL's `lower_case_table_names` variable and change condition
 on line 67.

Comment (by ramiro):

 (reformatted description)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9116: different caps in application name producing error

[Django]

#9116: different caps in application name producing error
--+-
  Reporter:  Maxim Syabro <[EMAIL PROTECTED]>  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Database layer (models, ORM) |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by kmtracey):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This has come up on django-users as well: http://groups.google.com/group
 /django-users/browse_thread/thread/9b3830c369a97f1a/37d3389f481c9b7c?

 I tend to think it's not necessary to put code in Django to deal with
 this.  People running MySQL on Windows can configure it to preserve the
 case of the table names it is given, or specify the all-lowercase name
 MySQL will use in the model's Meta db_table parameter, or just avoid using
 mixed-case in the app name.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~--~~~~--~~--~--~---