On 4/26/06, Robin Haswell <[EMAIL PROTECTED]> wrote:
We are planning on it, except the red thing that's annoying
I don't agree with that. He will probably (since he is use to control to the SQL) run tg-admin sql sql, and finally end up in sqlmeta class.
This is more something for someone new who is naive or doesn't remenber that "group by" is actually 2 reserved keywords in SQL.
The problem is that tg-admin sql create is actually a wrapper of I forgot the name, the actual command you use with SQLObject so this should be in the core of sqlobject not on tg side.
as much efficient as it is why will you want to run every query into a check for something that you will find out ones and will never forgot. It's like the tuple ones you learn ( ) is not what is in other languajes you never have to remind you of it again.
If the doc pages on SO in TG and SO had big fat red messages at the top of them warning about this,
then yes, perhaps, but as it stands they don't.
We are planning on it, except the red thing that's annoying
Also, an ex-manual SQL developer coming to TG would not probably think about the problems associated with using reserved keywords, as he/she's used to escaping them and would probably (and not unreasonably) assume that his ORM dealt with escaping
fields properly anyway.
I don't agree with that. He will probably (since he is use to control to the SQL) run tg-admin sql sql, and finally end up in sqlmeta class.
This is more something for someone new who is naive or doesn't remenber that "group by" is actually 2 reserved keywords in SQL.
IMO, if I were using SQL itself I wouldn't have a problem with reserved keywords. However TG
strongly recommends MVC with an ORM, and as such, should at least provide some contextual warning
about reserved keywords - if not at least on "tg-admin sql create".
The problem is that tg-admin sql create is actually a wrapper of I forgot the name, the actual command you use with SQLObject so this should be in the core of sqlobject not on tg side.
As has been pointed out - "if kw
in dict" is a very efficient operation in Python. In fact python has one of the most efficient
hashtable lookup algorithms in the known universe.
as much efficient as it is why will you want to run every query into a check for something that you will find out ones and will never forgot. It's like the tuple ones you learn ( ) is not what is in other languajes you never have to remind you of it again.
-Rob
Jorge Godoy wrote:
> Just because it doesn't fly it can't run? ;-) I don't believe that we have
> to make things worse to protect the developer from shooting himself, after
> all, as you said, such listings are freely available.
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
