Error on ydb.open(); YottaDB database connection cannot be reopened

[dlwicksell]

Error on ydb.open(); YottaDB database connection cannot be reopened

[faisalsami]

Yes that helps a lot thank you

…

On Tue, Sep 28, 2021 at 10:08 PM David Wicksell ***@***.***> wrote: Yes, there are a couple ways to handle this. First, if the database connection hasn't been opened, then the Nodem APIs will return with an exception, which you could catch in a *try/catch* statement, and then *open* the connection to the database before using the APIs, e.g. > const nodem = require('nodem').Ydb();undefined> nodem.get('^global'); Uncaught Error: YottaDB connection is not open> try { ... nodem.get('^global'); ... } catch (err) { ... nodem.open(); ... nodem.get('^global'); ... }1000 Second, the *version* API only reports the version of the underlying YottaDB or GT.M system, when the database connection has been opened, so you could search for the substring 'YottaDB Version' (or 'GT.M Version' when using GT.M), in the output of the *version* API, to determine if there is a current database connection, e.g. > const nodem = require('nodem').Ydb();undefined> nodem.version();'Node.js Adaptor for YottaDB: Version: 0.20.0 (ABI=93) [FWS]'> nodem.version().includes('YottaDB Version');false> nodem.open();{ ok: true, pid: 86593, tid: 86593 }> nodem.version();'Node.js Adaptor for YottaDB: Version: 0.20.0 (ABI=93) [FWS]; YottaDB Version: 1.32'> nodem.version().includes('YottaDB Version');true I hope that helps! I'm going to close this issue, as I believe I have addressed it sufficiently. Thank you. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADMJQXWBNXZZ6OSHBYT4P3UEHZB5ANCNFSM5E4WS77A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[dlwicksell]

Yes, there are a couple ways to handle this. First, if the database connection hasn't been opened, then the Nodem APIs will return with an exception, which you could catch in a try/catch statement, and then open the connection to the database before using the APIs, e.g.

> const nodem = require('nodem').Ydb();
undefined
> nodem.get('^global');
Uncaught Error: YottaDB connection is not open
> try {
... nodem.get('^global');
... } catch (err) {
... nodem.open();
... nodem.get('^global');
... }
1000

Second, the version API only reports the version of the underlying YottaDB or GT.M system, when the database connection has been opened, so you could search for the substring 'YottaDB Version' (or 'GT.M Version' when using GT.M), in the output of the version API, to determine if there is a current database connection, e.g.

> const nodem = require('nodem').Ydb();
undefined
> nodem.version();
'Node.js Adaptor for YottaDB: Version: 0.20.0 (ABI=93) [FWS]'
> nodem.version().includes('YottaDB Version');
false
> nodem.open();
{ ok: true, pid: 86593, tid: 86593 }
> nodem.version();
'Node.js Adaptor for YottaDB: Version: 0.20.0 (ABI=93) [FWS]; YottaDB Version: 1.32'
> nodem.version().includes('YottaDB Version');
true

I hope that helps! I'm going to close this issue, as I believe I have addressed it sufficiently. Thank you.