Goodnight to everybody
I think my problem with legacy databases with mysql is finished.
Change the driver SQLDB by DAL and now, my old application left to
give me the problem that I described above with web2py trunk version.
Thank you very much everybody and my apologize because I didn't see
I too have just been bitten by this.
From r2950 to current trunk, all fieldnames in queries have been .lower()d
This breaks my code which uses the real fieldnames - things like maxExtent
maxResolution.
This code all worked fine before on MySQL, PotsgreSQL sqlite.
In the spirit of not breaking
The change in trunk is supposed to only affect internals. If it breaks
you code than is is a bug. Please provide an example of code that
breaks and I will fix trunk.
Massimo
On Feb 1, 2:22 pm, Fran francisb...@gmail.com wrote:
I too have just been bitten by this.
From r2950 to current trunk,
Cool, thanks :)
This function:
http://bazaar.launchpad.net/~flavour/sahana-eden/trunk/view/head:/modules/s3/s3gis.py#L381
maxResolution maxExtent don't get copied into output as
maxresolution maxextent are in the Rows...
The relevant model:
This is now fixed in Trunk - thanks Massimo :)
F
Hi DenesL, This old application works now with with web2py 1.83.2 and
mysql in RedHat 5.5 with 64 bits
However, with web2py in trunk and mysql it doesn't works
De hecho en esta liga, te agradecí que sin querer me solucionaste un
problema :D
Hola Drayco,
aun no entiendo como funciona la aplicacion, el codigo que soporta
bases de datos pre-existentes para mysql simplemente no existe en el
archivo sql.py en la version 1.83.2, ni en dal.py en trunk.
Deben existir las definiciones para mysql de 'reference FK' (llave
foranea) y
Si el problema es con sequence_name entonces no tengo idea, jamas lo
he usado.
If the problem is with sequence_name then I don't know, I have never
used it.
On Jan 31, 10:47 pm, DenesL denes1...@yahoo.ca wrote:
Hola Drayco,
aun no entiendo como funciona la aplicacion, el codigo que soporta
this should now be fixed in trunk
On Jan 8, 2:58 pm, Thadeus Burgess thade...@thadeusb.com wrote:
All I know is that tables are issued as lowercase, but you can still access
your table as an uppercase attribute.
There is an inconsistency in the DAL somewhere because of this... Somewhere
it
Hi, I updated my trunk version
However, The same issue is still
This is the new traceback
Traceback (most recent call last):
File /home/drayco/web2py/gluon/restricted.py, line 188, in
restricted
exec ccode in environment
File /home/drayco/web2py/applications/iscada/models/cfedb.py, line
Are you sure it worked before?
As far as I know mysql is not supported for legacy DBs using
primarykey.
On Jan 28, 5:04 pm, drayco antrod...@gmail.com wrote:
Hi, I updated my trunk version
However, The same issue is still
This is the new traceback
Traceback (most recent call last):
Hi, Now my old application is work's with trunk.
Thank's a lot to fix it.
Hi, Now one of my old application is work's with trunk version.
Thanks a lot to fix it.
However I obtain the same issue with mysql and legacy database, this
is other old application, this is the issue
Traceback (most
Hi, When we have available that change?
And Can you give us a little example?
Because, I'm testing my application on the trunk version and I keep
getting the same error.
On Jan 8, 4:40 pm, Massimo Di Pierro massimo.dipie...@gmail.com
wrote:
We should have a flag to change this behavior
All I know is that tables are issued as lowercase, but you can still access
your table as an uppercase attribute.
There is an inconsistency in the DAL somewhere because of this... Somewhere
it is forgetting to convert to lower case. I don't know why converting table
names to lower case is forced
We should have a flag to change this behavior DAL(...,lowercase=True).
I would take a patch.
On Jan 8, 2:58 pm, Thadeus Burgess thade...@thadeusb.com wrote:
All I know is that tables are issued as lowercase, but you can still access
your table as an uppercase attribute.
There is an
Probably just being unhappy with the case :)
tecnoGradua != tecnogradua
Mart :)
Field(tecnoGradua, 'string',
On Jan 8, 12:57 am, drayco antrod...@gmail.com wrote:
Hi, this code works with web2py 1.89.5 with mysql
but with web2py in trunk and mysql it dosent works.
Ok, I understand your point.
But this is a issue of DAL or what?
because I only update web2py to trunk version
On Jan 8, 12:15 am, mart msenecal...@gmail.com wrote:
Probably just being unhappy with the case :)
tecnoGradua != tecnogradua
Mart :)
Field(tecnoGradua, 'string',
On Jan 8,
no, this is python...
not sure how it could have worked before, but the key (technogradua)
in .keys() is not being picked up... dal is simply pointing that out
with the exception being thrown. I did notice when I made the switch
that a few more of my mistakes got picked up (or it could be that I
I can also confirm this is a bug with the new DAL.
It is only caused when using upper case characters in the table or field
names. It seems that web2py converts all of the tablenames to lower case
when issuing the SQL (so your actual tables are lower regardless of what you
specify in the python).
really? I didn't know, thanks for pointing that out...
just out of curiosity
in
in __getitem__
return dict.__getitem__(self, str(key))
KeyError: 'tecnogradua'
don't the attribute lookups get done by python ultimately? Just
trying to understand...
how could this have worked if doing
20 matches
Mail list logo
