Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modeling a new table in an existing db got issue #45

Closed
jasonandjack1997 opened this issue May 20, 2018 · 3 comments
Closed

modeling a new table in an existing db got issue #45

jasonandjack1997 opened this issue May 20, 2018 · 3 comments
Labels

Comments

@jasonandjack1997
Copy link

First I do this:

nSQL("table1")
.model([
{ something}
])
.config({
id: "myDB1",
mode: "PERM",
history: false
})
.connect();

then I do
nSQL("table2")
.model([
{ something}
])
.config({
id: "myDB1",
mode: "PERM",
history: false
})
.connect();

An error will occur saying something like could not find store object. Then I have to change db to a new name. The other way is delete the indexedDB in chrome dev and build the tables again.

@jasonandjack1997
Copy link
Author

jasonandjack1997 commented May 21, 2018

The error message is
app.js:66916 Uncaught (in promise) DOMException: Failed to execute 'transaction' on 'IDBDatabase': One of the specified object stores was not found.
at _IndexedDBStore.store (http:///js/app.js:66916:36)
at getIDBIndex_1 (http://
/js/app.js:66886:27)
at http:///js/app.js:66902:21
at http://
/js/app.js:12181:13
at new Promise ()
at http://js/app.js:12180:16
at Array.map ()
at Object.exports.fastALL (http://
/js/app.js:12179:46)
at IDBOpenDBRequest.idb.onsuccess (http://*****/js/app.js:66901:29)

@only-cliches
Copy link
Owner

Hey thanks for the bug report! This issue has been resolved in version 1.6.2, if you npm install from github you'll get the fix.

I'm going to try to get 1.6.2 on NPM by the end of the week.

@only-cliches
Copy link
Owner

Marking this as resolved since there's been no response for several days. Feel free to reopen the issue if you run into the problem again/have more questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants