#201: SQLObject does not catch SQL keywords used as names in models
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 0.9
Component: SQLObject | Version:
Severity: minor | Resolution:
Keywords: |
-----------------------+----------------------------------------------------
Changes (by godoy):
* severity: critical => minor
Comment:
Thinking better, this isn't "critical" but it is definitely annoying (the
use of reserved SQL keywords). Another problem is also related to
database extensions (i.e. some reserved keyword a database has that other
doesn't have and isn't in the SQL standard...). I don't think it is
feasible to check all tables that would be created (either through direct
name mungling or through sqlmeta class) against a table of "forbidden
names" and emmiting an error message. It is, IMHO, the developer's
responsability to avoid using reserved names or defining some unique
naming scheme to avoid that.
With regards to using quotes all the time, this might solve the problem
but might lead to other problems when integrating your application with
legacy databases or with reusing the new database with other external
applications.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/201>
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
-~----------~----~----~----~------~----~------~--~---
