You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many non-SQL databases use column names with underscores at the begining(PouchDB's _id field, etc). Is there a specific reason the schemas don't support this, or any flag to enable it?
The text was updated successfully, but these errors were encountered:
if (!modelData[0] || modelData[0].match(/[\(\)\]\[\.]/g) !== null || modelData[0].indexOf("_") === 0) {
hasError = true;
rej({ error: "Invalid Data Model at " + (table.name + "." + col) + "! https://docs.nanosql.io/setup/data-models", query: _this.query });
}
If I alter the code to exclude the check for the undescore prefix then it works perfectly fine. Maybe one of the adapters does not like it, in which case it would be possible to then add a config for it to allow it.
UPDATE: So after further investigation it seems that nano-sql uses underscores internally for table creation (I observed with SQLite) and it disallows using underscores for table and db names so as to avoid collisions most probably..
Many non-SQL databases use column names with underscores at the begining(PouchDB's _id field, etc). Is there a specific reason the schemas don't support this, or any flag to enable it?
The text was updated successfully, but these errors were encountered: