ssage-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Monday, July 22, 2019 7:03 PM
To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
Well no luck so far on the Direct_DBMS action.
Tried with a
> From: Wayne Irvine [mailto:wa...@byteserve.com.au
> <mailto:wa...@byteserve.com.au>]
> Sent: Thursday, July 25, 2019 4:03 PM
> To: TeraScript-Talk@terascript.com <mailto:TeraScript-Talk@terascript.com>
> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>
&
Yes that should work. I suspect it's a bug in TS.
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Thursday, July 25, 2019 4:03 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
Ok, so in theory should this work?
What am I missing
normally, in the query below there are none, so
> nothing should've been reported.
>
> From: Wayne Irvine [mailto:wa...@byteserve.com.au]
> Sent: Wednesday, July 24, 2019 6:43 PM
> To: TeraScript-Talk@terascript.com
> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>
Wednesday, July 24, 2019 6:43 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
<@SQL> just gives the same string as the DEBUG information.
It gives no information on how the t1 alias is set up (unless ‘FROM testtable
t1’ is how it is d
e.com.au]
> Sent: Monday, July 22, 2019 7:03 PM
> To: TeraScript-Talk@terascript.com
> Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
>
> Well no luck so far on the Direct_DBMS action.
>
> Tried with a fresh new table and very simple SQL statement and got the same
You can see generated SQL with @SQL and @BOUNDVALS, just output those tags
immediately after the query.
-Original Message-
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Monday, July 22, 2019 7:03 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time
Well no luck so far on the Direct_DBMS action.
Tried with a fresh new table and very simple SQL statement and got the same
error.
I would really love a way to actually log the SQL statement generated and sent
by the Search Action. The one in the Debug uses aliases and you can’t see the
steps
Wayne,
I recall needing to adjust datatype(s) in FM databases to work correctly
with Wtango and JDBC/ODBC.
Perhaps a test FM db with only integer columns.
- Steve K
On 7/10/19 7:06 PM, ubslab wrote:
> Wayne,
>
> Are you able to connect to FM table.columns in the Terascribe editor
> JDBC/ODBC
> On 11 Jul 2019, at 12:38 am, Robert Shubert wrote:
>
> Wayne,
>
> First do a simple query like "SELECT 1" just to double check the DBMS.
I tried:
SELECT 1
SELECT 1 FROM Packages
both gave an error.
>
> Then try grabbing just one row "SELECT packagename FROM Packages WHERE
> packagename =
I hadn’t noticed the user vars previously. They are left over from previous
searches with the Search action. I added a Purge as the first action and they
no longer appear.
I also changed the Select to retrieve a field that is not user generated, so
more predictable and alphanumeric.
Still
uesday, July 09, 2019 11:34 PM
To: TeraScript-Talk@terascript.com
Subject: Re: TeraScript-Talk: First time doing Direct_DBMS
> On 10 Jul 2019, at 4:26 pm, ubslab wrote:
>
> Wayne,
> So none the following forms will work in the action?
>
> SELECT packagename FROM Packages
>
Error
An
If the expected result set is in the range of "[Array:553x36]" I would
suspect characters that the ODBC/JDBC connector can't pass or parse.
Is it reasonable to refill the database with values not containing
special, symbol, or punctuation characters to diagnose?
Had a similar issue with a FM
> On 10 Jul 2019, at 4:26 pm, ubslab wrote:
>
> Wayne,
> So none the following forms will work in the action?
>
> SELECT packagename FROM Packages
>
Error
An error occurred while processing your request:
File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101
14 matches
Mail list logo
