[wp-trac] [WordPress Trac] #6492: Guids No Longer Have Permalink Format
WordPress Trac
wp-trac at lists.automattic.com
Sun May 8 07:45:25 UTC 2011
#6492: Guids No Longer Have Permalink Format
-------------------------------------+------------------------------
Reporter: brianwhite | Owner: anonymous
Type: enhancement | Status: reopened
Priority: normal | Milestone: Awaiting Review
Component: General | Version: 2.5
Severity: trivial | Resolution:
Keywords: has-patch guid featured |
-------------------------------------+------------------------------
Comment (by Denis-de-Bernardy):
Replying to [comment:60 westi]:
> I'm not sure there is significant benifit for most installs in switching
to UUID which from what I can tell from a quick google is mysql specific
so UUID generation would probably have to become part of the wpdb
interface.
On the small benefit, I tend to agree, since the core devs expressed no
interest in using it downstream in the editor and introduced the new draft
types instead. Re-opening this ticket feels a bit like beating a dead
horse, so suggesting we close it back (possibly with a filter as you
suggest).
Your Googling is giving you incorrect impressions, by the way.
For one, other DB products support it under other names: GUID, UUID,
Identity, Unique Identifier, etc. More importantly, it has less to do with
being a native DB type (leading to efficient storage and indexing) than it
has to do with having a means to generate a unique number that can be used
as a surrogate key on distributed systems.
With respect to the latter point, PostgreSQL offers the UUID type but no
means to generate one unless you install a contrib module. Best I
recollect the pg-hackers discussion, one of the arguments was that
generating them can, and usually should, be done at the application layer
anyway.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/6492#comment:61>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list