On 11/11/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On Nov 11, 2005, at 1:54 PM, pbx wrote: > > Actually, Ian's idea was part of my original thinking as well -- if > > you > > make "__exact" optional, you can completely remove "pk" (which is > > itself a weird exception to the keyword rules). > > Except if you remove "__exact" then you can't have fields named > "select", or "tables", or "fields", or...
Aren't certain names going to be disallowed anyways due to SQL keywords? If so, then on top of fields like this: select, order, limit, offset, from, where, join, and distinct. there will be a few django specific words such as order_by, tables, and fields that are disallowed. Of course its not good to lose out on a few extra words, but as long as there are some unavailable then its not as "inconsistent" to have a few extra names that don't work. Of course, these names would have to be blocked during the "install" rather than simply allowing the create table statement to fail like it does for the SQL errors. Either way, its not a big deal, all I know is I would like to save typing 7 or 14 characters for 80+% of my get statements. -ian
