[TurboGears] Re: [Docs] do NOT use Group or Order as SQLObject classes

Thu, 20 Apr 2006 15:06:07 -0700

On 4/20/06, Robin Haswell <[EMAIL PROTECTED]> wrote:

Jorge Vargas wrote:
> This is a recurrent question/problem in the mailing list.
>
> People went starting to work on identity will probably name their class
> Group.
> People that are probably testing TG will want to make a shopping cart or
> something similar and will probably come up with the Order class

This is not user error, this is a bug in SQLObject. Field names should be properly quoted (backticks
in MySQL).

I will not say it's a bug, it's more a design thing, if they didn't do it for any reason (performance may be one) we need to investigate. For now it's a user error, if it's get change in SQLObject we'll come back here and post this is not an issue anymore :)

I'm not aware of any SQL database which imposes restrictions on table and column names.

The fact they allow non quoted names means a restriction for keywords.

Table and column names should always be quoted in SQL on general principal.

Not really, it's a "good practice" but you know how those are

I will file a bug.

I was going to do that but the tracker was down so I posted to the mailing list.

-Rob


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to