Hi Massimo,
Solved the issue.
The new widget / ajax is looking for a ID in the table. I just added
the id to the view, and it works fine!
regards
Martin
On Thu, Nov 17, 2011 at 2:45 PM, Massimo Di Pierro
massimo.dipie...@gmail.com wrote:
Can you helps us debug? Use chrome, check out the callback url, call
it directly, does it return a ticket?
On Nov 17, 1:53 am, Ole Martin Maeland olemael...@gmail.com wrote:
Hi Massimo,
upgrade from version 1.89.5 (2010-11-21), so old version.
I have tried to substitute the built in autocomplete with s-cubism
suggest_widget. It works the same way - no function when I try to read
from db view, but works fine when directly from db.
regards
Martin
On Thu, Nov 17, 2011 at 7:47 AM, Massimo Di Pierro
massimo.dipie...@gmail.com wrote:
what did you upgrade from?
On Nov 16, 3:07 pm, Ole Martin Maeland olemael...@gmail.com wrote:
Hi,
I upgraded web2py to latest version. everything works fine exept the
autocomplete widget
I use MySQL as my database.
The autocomplete is reading from a db VIEW. The reason for this is
that I have 2 columns in a db:
short_name and ISIN that is the name, and ISIN that is the ID. By
doing union select it worked fine until I upgraded.
after the upgrade to the latest version it is not recognising the VIEW
as a DB. in my db setup I have set it to be a DB with migrate=False.
I have tried to use the widget directly with a DB, and then it works fine.
Initially I thought the problem were due to new adapter: pymysql, but
I have changed it using:
import MySQLdb
from gluon.dal import MySQLAdapter
MySQLAdapter.driver = MySQLdb
but that is not the problem.
It does not read the VIEW as a DB anymore..
I have several VIEW's in my DB and it works fine for all other queries..
any idea how to fix it ?
regards
martin
--
Hilsen
Ole Martin
Mob: 95227471
--
Hilsen
Ole Martin
Mob: 95227471
