[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-26 Thread Rahul
This information is awesome. Thank you for sharing this with us. Glad I am coding web2py. Cheers, Rahul On Thursday, July 26, 2018 at 3:09:35 AM UTC+5:30, Anthony wrote: > > On Wednesday, July 25, 2018 at 3:36:58 PM UTC-4, pbreit wrote: >> >> ...or Anthony! >> >> Thanks, that's good info and re

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread Anthony
On Wednesday, July 25, 2018 at 3:36:58 PM UTC-4, pbreit wrote: > > ...or Anthony! > > Thanks, that's good info and reassuring. > > Safe to assume little/no downside to always double-quoting? > It's the default behavior of web2py now, so hopefully not. -- Resources: - http://web2py.com - http://

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread pbreit
...or Anthony! Thanks, that's good info and reassuring. Safe to assume little/no downside to always double-quoting? -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report I

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread Anthony
See also https://groups.google.com/d/msg/web2py/lPcl3CrfnDs/J0zqHf8DAwAJ. On Wednesday, July 25, 2018 at 2:23:58 PM UTC-4, Anthony wrote: > > On Wednesday, July 25, 2018 at 1:54:56 PM UTC-4, pbreit wrote: >> >> I feel like I've heard before that we no longer need to worry about >> reserved words

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread Anthony
On Wednesday, July 25, 2018 at 1:54:56 PM UTC-4, pbreit wrote: > > I feel like I've heard before that we no longer need to worry about > reserved words which would be awesome. I'm going to try that on my projects > and see if I run into any issues. > > Is this something that Massimo or Giovanni c

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread pbreit
I feel like I've heard before that we no longer need to worry about reserved words which would be awesome. I'm going to try that on my projects and see if I run into any issues. Is this something that Massimo or Giovanni could confirm? -- Resources: - http://web2py.com - http://web2py.com/book

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread Anthony
On Wednesday, July 25, 2018 at 8:51:26 AM UTC-4, Rahul wrote: > > Hi Anthony, pbreit, >The following line of code works just fine for *rname*. I was able > to save *state*, *date*, *module*, *notify *etc in the database table as > field names. Although I will make it a practice to use di

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-25 Thread Rahul
Hi Anthony, pbreit, The following line of code works just fine for *rname*. I was able to save *state*, *date*, *module*, *notify *etc in the database table as field names. Although I will make it a practice to use different field names than those reserved/unreserved for future projects.

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-24 Thread Anthony
I believe the DAL now always double quotes table and field names when constructing queries, so I'm not sure you even need to use check_reserved anymore. What happens if you simply remove it? Anthony On Tuesday, July 24, 2018 at 4:39:05 PM UTC-4, pbreit wrote: > > Apparently if you are going to

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-24 Thread pbreit
Apparently if you are going to use "rname" you may need to surround the column name with single and double quotes which will send the double-quotes to the DB: Field('state', rname='"state"') As an aside, it always seemed to me that a DB access library would be able to be structured in such a w

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-24 Thread Rahul
All, To add - Syntax like below worked however I am getting a few application errors. Field(‘notifys’ , ‘boolean’, rname=‘notify’), In above notify is a reserved postgres keyword but we can use it as a field name in postgres db table. The reference field name ‘notifys’ in this case is some

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-24 Thread Rahul
Thank you! for getting back Dave and pointing me to this page - I used it for *state *field name and it did *not *work for me. Field('state', rname='state_country'), Give me below syntax error still - *SyntaxError*: invalid table/column name "state" is a "POSTGRES_NONRESERVED" reserved SQ

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-23 Thread Dave S
On Sunday, July 22, 2018 at 10:28:46 PM UTC-7, Rahul wrote: > > Hey everyone, > Any clues on this one? OR should I start updating the > application and the models with unused field names? Please let me know > > > Does 'rname' help? You have to poke a bit in the book to find it at fie

[web2py] Re: Dealing with reserved keywords when you change or upgrade your database from SQLite to POSTGRES

2018-07-22 Thread Rahul
Hey everyone, Any clues on this one? OR should I start updating the application and the models with unused field names? Please let me know Thank you, *Rahul* On Friday, July 20, 2018 at 12:40:04 PM UTC+5:30, Rahul wrote: > > Hello All, >I am migrating my proj