Yes, that seems to have fixed it. Thanks!
I think I fixed it. All but oracle expect SQL to be ; terminated.
web2py adds the ; and removes it for Oracle. Because of a type it was
not adding it so it was removing the last char thinking it was a ;.
On Aug 25, 6:40 pm, Tim Korb wrote:
> I did this, but am not sure what I'm looking for. Thi
I did this, but am not sure what I'm looking for. This appears...
function:
select
and
last_query:
db.auth_user.id>0
for example, and lots of other settings, etc. But I don't see anything that
looks like an actual SQL query.
So, working with one of my colleagues, we added tracing to dal.p
Can you add
{{=response.toolbar()}}
somewhere in your layout.html and see what is the invalid query
generated by appadmin?
On Aug 25, 9:23 am, Tim Korb wrote:
> I am using this this version...
>
> changeset: 2295:7c7f7d5ac882
> date: Wed Aug 24 16:25:41 2011 -0500
>
> I am able
I am using this this version...
changeset: 2295:7c7f7d5ac882
date:Wed Aug 24 16:25:41 2011 -0500
I am able to reproduce the problem by creating a simple, default app and
replacing the DAL line with...
from gluon.custom_import import track_changes
track_changes()
fr
can you tell me which web2py version (number and date) and list of
steps to reproduce the problem?
On Aug 24, 8:49 pm, Tim Korb wrote:
> I'm getting the same error (Invalid Query ORA-00907: missing right
> parenthesis) when using the admin interface to access tables for a
> newly-created Oracle d
I'm getting the same error (Invalid Query ORA-00907: missing right
parenthesis) when using the admin interface to access tables for a
newly-created Oracle database (without primarykey setting).
I do not think primarykey is supported on Oracle. We can do this
quickly but we will need your help with tests.
@Denes, can you help with this as well?
On Aug 23, 10:14 pm, tomt wrote:
> I recently tried to access some legacy tables in an Oracle database
> with web2py. The connection string and m
8 matches
Mail list logo