In agreement with you on not enforcing this - jsonb - as default, but something that a knowledge-able developer can turn on as a configuration / code option, and specifically for the PG db.
On Friday, January 30, 2015 at 1:35:26 AM UTC+5:30, Niphlod wrote: > > that basically sums the whole thing to "until now you could have stored > the hell you wanted in json, while from now on you'll have this > limitations". Still think that cutting options by default is a good thing > to do ? I could be +1 for adoption as an option, but -1000 for making it > the default, given also that ATM it's the only backend supporting it. > -- 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 Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
