The alias t1 is set in the query by having it follow the table name, so yes, "FROM test t1" is creating the alias t1
@BOUNDVALS should work 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 <@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 done). Either way, this statement used in the Direct_DBMS action results in an error still. <@BOUNDVALS> is pink in Terascribe and ignored by Terascript. Wayne On 24 Jul 2019, at 12:01 am, Robert Shubert <rshub...@tronics.com <mailto:rshub...@tronics.com> > wrote: 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 <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 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 beforehand to test it out. Wayne On 12 Jul 2019, at 10:23 am, Wayne Irvine <wa...@byteserve.com.au <mailto:wa...@byteserve.com.au> > wrote: This is Mac OSX Sierra Server 10.12.6 and Filemaker Server Advanced 12. What i would like to be able to log is the call the Search action makes to the JDBC plugin. Then I could emulate tis is a Direct_DBMS action and modify from there. One thing that has got me thinking is the actions next to Direct_DBMS. Begin_Transaction and End_Transaction. Do these need to be before and after the Direct_DBMS action? I’ve never seen documentation for how these work. Wayne On 12 Jul 2019, at 9:12 am, ubslab <ubs...@uw.edu <mailto:ubs...@uw.edu> > wrote: Wayne, Am I correct assume this is all on a MacOS server? If so, which version of OS and FileMaker are you using? - Steve K On 7/10/2019 7:18 PM, ubs...@uw.edu <mailto:ubs...@uw.edu> wrote: 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 panel? - Steve K On 7/10/19 6:45 PM, Wayne Irvine wrote: On 11 Jul 2019, at 12:38 am, Robert Shubert <rshub...@tronics.com <mailto:rshub...@tronics.com> > 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 = '{known name}’" SELECT packagename FROM Packages WHERE packagename = 'Kessell Run’ Error If that works, then we may be looking for a bug dealing with non-value. Try "SELECT packagename FROM Packages WHERE packagename IS NOT NULL” SELECT packagename FROM Packages WHERE packagename IS NOT NULL Error What version of TS are you running? There was a JDBC fix in 7.1.1 and I have another fix (which may be your problem) coming in 7.1.5. 7.1.3.1 Wayne Byteserve Pty Ltd w: http://www.byteserve.com.au/ e: i...@byteserve.com.au <mailto:i...@byteserve.com.au> p: +61 02 9960 6099 m: 0409 960 609 f: +61 02 9960 6088 ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. Byteserve Pty Ltd w: http://www.byteserve.com.au/ e: i...@byteserve.com.au <mailto:i...@byteserve.com.au> p: +61 02 9960 6099 m: 0409 960 609 f: +61 02 9960 6088 ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. Byteserve Pty Ltd w: http://www.byteserve.com.au/ e: i...@byteserve.com.au <mailto:i...@byteserve.com.au> p: +61 02 9960 6099 m: 0409 960 609 f: +61 02 9960 6088 ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. Byteserve Pty Ltd w: http://www.byteserve.com.au/ e: i...@byteserve.com.au <mailto:i...@byteserve.com.au> p: +61 02 9960 6099 m: 0409 960 609 f: +61 02 9960 6088 _____ To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com with "unsubscribe terascript-talk" in the body.
