Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 I have written a UUID Field tha supports django 1.7 and python 3.4
 https://github.com/japrogramer/django-uuid-contour

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/091.ad1dc36653f718f99d8d102e0f4f8c13%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Natim87):

 Any news about that ?

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/091.5fed6ad3bf38c4e63d33af1565333e57%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by iamio@…):

 Glad to hear that UUID is hopefully coming to the core.

 I just came across this problem developing an online store. Purchase
 orders are referenced by the AUTO INT field, but then this exposes a lot
 of information to end users. A malicious end user will know every primary
 key in my table, and business competitors can discover how many
 transactions that the store processes online. Even if it is easy for a
 user to create a UUID field, AUTO INT fields are less secure than UUID's,
 so Django should be '''discouraging''' the use of AUTO INT for any primary
 key that is visible to end users.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by guettli):

 I created a new ticket: #19463

 Jacob has announced that UUID field could be added to core.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Old Django user here :-)

 To my knowledge, there is no 3rd party implementation that uses native
 SDBG UUID types. Current implementations subclass Charfield, because it's
 the easy thing to do, but it's slow.

 First, given the way we ./manage.py dumpdata to JSON, it causes many
 problems with AUTO INT as primary keys when loading back data. Using a
 UUID solves this.

 Secondly, having no standard way to use UUID as primary key for stuff like
 auth.User, perms and groups is really a bummer (ever try to share test
 data with perms with your fellow coworkers ?), and is a direct consequence
 of the fact that UUID are not part of the Django core: nobody ever think
 about them. Some thing goes with URLs: we got slugs and ids for URL, but
 we won't include a UUID in it (it's ugly). Nobody will try to think of an
 elegant solution to that before it becomes so natural to have UUID that
 you are forced to wonder. Beginers don't even know UUID are an options,
 it's a real shame.

 Thirdly, UUID are now core part of big websites since they are more or
 less required for serious database replication, sharding, and sharing a
 common reference accross different databases (especially NoSQL).

 It's really becoming a requirement, not an option. Not having it in the
 core 3 years ago would have make sense, but in 2012 you do expect this
 from a Web framework. I've seen more people using UUID than python 3 or
 asynchronous requests handling, and the two are now on the TODO list while
 being much more costly to develop.

 I know you have limited ressources and want to limit the number of things
 in the framework. No hard feelings there. It's just it's worth considering
 it again: the Web is a different place now than 5 years ago, when it was
 set to "won't fix".

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 +1

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 New Django user here. Considering all of the features I've read about in
 Django, I was thoroughly surprised & disappointed to find UUIDs are not
 part of its core.

 The ease of adding a custom field is beside the point. UUIDs have their
 place and I fail to see a valid reason we should have to jump through
 hoops to use such a common field.

-- 
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] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 If you want that the won't fix decision to be reevaluated, please discuss
 it first on the django-developers mailing list.

-- 
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] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 I vote++ on this.

 In 2012 it is definitely worth considering adding UUID as a field type in
 the core Django codebase. Many of the Django DB backends now support UUID
 as a real type (read: 1st rate, optimized, indexed >> the PG 128bit field
 is a backend implementation example).

 I know it is easy to implement or pull in from django_extensions but,
 seriously, UUIDs are not just CharFields in some of these backends. Isn't
 it time that django seriously considers growing up with the DBMS that it
 supports?

 Thanks!

-- 
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] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by ragi@…):

 If it were in core, then Django could leverage the 128bit field in
 PostgreSQL which would speed up most queries that rely on this field.
 Please note that people that use uuid as a field, it is most likely
 because they are using it as a key in their queries. Please consider re-
 opening.

-- 
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] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * 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] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
   Reporter:  John   |  Owner:  nobody
  Downey | Status:  closed
   Type: |  Component:  Database layer
  Uncategorized  |  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  uuid field
 Resolution:  wontfix|  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 佳き日に、二人に送るhttp://www.d-mailer.com/";>電報 結婚 文例でお祝いの気持ちを伝える。

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