#658: [PATCH] identity framework makes use of "Deprecated" visit.id field
-----------------------------+----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Type: defect | Status: new
Priority: high | Milestone: 0.9
Component: Identity | Version: 0.8
Severity: normal | Resolution:
Keywords: identity visit |
-----------------------------+----------------------------------------------
Comment (by [EMAIL PROTECTED]):
It's not evil to use the visit.id field IMO, but it currently raises a
Deprecation warning. I personally would rather use the id as it gives me
(using the python database bindings that I use) easier access to the data.
The number of visit plugins that exist in the wild right now is probably
very small. If to the tg_admin script a routine was added to drop and
recreate the visit table, the "upgraded" app would start with no sessions
(session data is temporary by definition anyway).
How would you know if code used the old method?
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/658>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
