[web2py] Re: GAE - SQL cloud connection

2012-11-16 Thread rif
Done (http://code.google.com/p/web2py/issues/detail?id=1172) Are the migrations issues to GoogleSQL still present? -rif vineri, 16 noiembrie 2012, 12:57:14 UTC+2, Massimo Di Pierro a scris: > > Please open a ticket and we will fix this asap. > > On Friday, 16 November 2012 04:49:35 UTC-6, rif wr

[web2py] Re: GAE - SQL cloud connection

2012-11-16 Thread Massimo Di Pierro
Please open a ticket and we will fix this asap. On Friday, 16 November 2012 04:49:35 UTC-6, rif wrote: > > I created today a sql cloud database. And I got the same error. > > I changed to path VARCHAR(255) and now it works. Anybody else having the > same problem? > > -rif > > marți, 7 august 2012

[web2py] Re: GAE - SQL cloud connection

2012-11-16 Thread rif
I created today a sql cloud database. And I got the same error. I changed to path VARCHAR(255) and now it works. Anybody else having the same problem? -rif marți, 7 august 2012, 18:27:13 UTC+3, Massimo Di Pierro a scris: > > Why does 512 result in "Specified key was too long; max key length is

[web2py] Re: GAE - SQL cloud connection

2012-08-07 Thread Massimo Di Pierro
Why does 512 result in "Specified key was too long; max key length is 767 bytes". Is one counting unicode and one bytes? If setting this length to 128 is the only option, I will change it but I am afraid it may be too short to store .table files. Did you encounter any problem after this change?

[web2py] Re: GAE - SQL cloud connection

2012-08-07 Thread Alexei Vinidiktov
The problem still exists in the latest nightly build. Without this modification (changing the field length to 128) launching web2py on the remote GAE server gives me the error: DatabaseError: 1071: Specified key was too long; max key length is 767 bytes The whole traceback is as follows: Trac

[web2py] Re: GAE - SQL cloud connection

2012-01-06 Thread howesc
i don't know if i'm gonna regret this later, but in dal.py i changed that field length to 128: self.db.executesql("CREATE TABLE IF NOT EXISTS web2py_filesystem (path VARCHAR(128), content LONGTEXT, PRIMARY KEY(path) ) ENGINE=InnoDB;") now it works again.

[web2py] Re: GAE - SQL cloud connection

2011-11-10 Thread pallav
Hi Massimo, I just ran into the same issue on GAE SQL. Any update/ideas since the last post? I'm happy to help code/debug/brainstorm. Thanks, Pallav On Oct 19, 10:53 am, Massimo Di Pierro wrote: > This is another of those weird mysql issues > > CREATE TABLE IF NOT EXISTS web2py_filesystem (path

[web2py] Re: GAE - SQL cloud connection

2011-10-19 Thread Massimo Di Pierro
This is another of those weird mysql issues CREATE TABLE IF NOT EXISTS web2py_filesystem (path VARCHAR(512), content LONGTEXT, PRIMARY KEY(path)); results in DatabaseError: 1071: Specified key was too long; max key length is 767 bytes I need to think about a workaround I have been running on