Re: Node.js result set question - Trimming blanks

If I'm reading the docs correctly:

1.3.15. execute

*Description:*

Runs a statement that was successfully prepared using *prepare*() once or
multiple times. The statement is processed with the current values of any
application variables that were bound to parameter markers by *bindParam*().

*Syntax 1:*

execute()

*Syntax 2:*

execute(function *Callback*(*OutParamList*))

*Parameters **Callback*(*OutParamList*):

*Callback *is a callback function to process the output parameters of the
parameter markers. *OutParamList *is a list of the output parameters. It is
in the java script array format.

*Comments:*

* If the statement also return a result set, user can issue the fetch()
function to retrieve the data row by row.


I believe This is saying that when using execute on a prepared statement vs
exec on an SQL statement the rows NEEDS be processed one at a time.

bummer.. returning the entire result set made things so easy to throw into
a jade template. :) Now I'm going to need to change how that's done. I
was wondering what was better practice, looping your result set records in
the node.js or letting your template handle it...

On Mon, Apr 4, 2016 at 9:17 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

That does seem to work, but I'm interested in getting the entire result
set like when you just use db.exec with an SQL statement.

Is that not possible? I notice you're not using the callback. Or I'm
misunderstanding the use of the callback. :) This does help, though. I
will dig deeper.

On Mon, Apr 4, 2016 at 8:57 AM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:

Check out this example:

var db = require('/QOpenSys/QIBM/ProdData/Node/os400/db2i/lib/db2')
try{
db.init();
db.conn("*LOCAL");
var sql = 'select * from QIWS.QCUSTCDT where LSTNAM like ?'
db.prepare(sql)
db.bindParam([
['%S%', db.SQL_PARAM_INPUT, 0]
])
db.execute();
var rc;
do{
rc = db.fetch(function callback(row) {
console.log(row);
});
} while(rc != db.SQL_NO_DATA_FOUND);
db.close();
} catch(e) {
db.close();
console.log(e);
}

Aaron Bartell
litmis.com - Services for open source on IBM i


On Mon, Apr 4, 2016 at 7:11 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

That makes sense about the varchar. ... thanks.

Still getting nothing in my result sets. See anything wrong with my
prepared statement? Debug looks good.

Connect to *LOCAL
Connected to *LOCAL with ID .
SQL: select CMEMAIL, CMLNAME, CMFNAME, CMFCOMP, CMFADD1, CMFADD2,

CMFCITY,

CMFSTATE, CMFZIP, CMFCNT, CMNOTES from bvscomp.cstmstpf where
UCASE(CMEMAIL) like ?
Bind Parameter [1] = %STONE%
SQLExecute() rc=0.
SQLRowCount() rc=0.

var sql = 'select * from cstmstpf where UCASE(CMEMAIL) like ?';

db.init();
db.conn(DBname);
db.prepare(sql);
db.bindParam([
['%' + email + '%', db.SQL_PARAM_INPUT, 0],
]);

try {
db.execute(function callback(out) {
console.log(out);
res.render('customerList', {customerList: out});
});
} catch(e){
console.log('error: ' + e + ' for sql statement ' + sql);
}

I've tried a few different SQL statements, even ones without any

parameters

and they don't work when using the prepare... but if I run the same SQL
statement through exec it works fine.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.