Error Message Running Tutorial

Post any questions you have about using the Verj.io Studio, including client and server-side programming with Javascript or FPL, and integration with databases, web services etc.

Moderators: Jon, Steve, Ian, Dave

Joe Blake
Ebase User
Posts: 44
Joined: Sun Sep 15, 2013 6:26 pm

Error Message Running Tutorial

#1

Postby Joe Blake » Tue Oct 08, 2013 7:24 pm

I am at the end of the TABLES TUTORIAL. When I run my form, I get the following error message:

SQL error reading from database resource MYCDS ,Syntax error: Encountered "%" at line 1, column 41.


In attempting to research the problem, I look in MYCDS and find this:

&&WHERE_CLAUSE

in the where clause section.

Confirming this should be the value, I go back to the tutorial,

hhttp://dev-docs.verj.io/ufs/doc/tables_tutorial.htm

in this section

Making the table searchable

and find this instruction:

Add ‘&&WHERE_CLAUSE’ to the where clause section of the resource.


So, not knowing what to do I deleted the &'s one at a time and rerun the form to know avail.

[Off subject, but interesting: Without any &'s the following message appeared:

"SQL error reading from database resource MYCDS ,Column 'WHERE_CLAUSE' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE statement then 'WHERE_CLAUSE' is not a column in the target table."

Wow....I don' know who wrote this, but he certainly put a lot of thought into this statement. And more importantly, how often do you think anyone ever sees this message?]

In any case, where else might I look to correct this issue.

Thanks.
0 x
New Potential User.

User avatar
Wai
Moderator
Moderator
Posts: 165
Joined: Wed Sep 12, 2007 9:04 am
Location: Sandy, UK
Contact:

#2

Postby Wai » Wed Oct 09, 2013 8:13 am

It's probably a missing quote/apostrophe in your SQL.

The && notation is used to substitute a value into the resource field at runtime.

Therefore, in the example, you are building up your where clause dynamically in your script and passing it through to the resource.

The easiest way to debug these issues is to turn debug on the resource (debug checkbox on the resource), and view the SQL that is generated in the execution log.

You will then be able to see what;s wrong in the SQL.
0 x


Who is online

Users browsing this forum: No registered users and 5 guests