Skip to content

Commit f4d2e91

Browse files
committed
Remove NanoSQL issue from README
1 parent 4d144bb commit f4d2e91

File tree

1 file changed

+0
-13
lines changed

1 file changed

+0
-13
lines changed

README.md

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -332,19 +332,6 @@ Before requesting user's current location some options can be customized in orde
332332
| acquireLocation(options: [AcquireOptions](#geolocation-acquire-options) | `Promise<Geolocation>` | Allows to obtain user's current location |
333333
| locationStream(options: [StreamOptions](#geolocation-stream-options) | `Observable<Geolocation>` | Allows to actively obtain user's location updates |
334334

335-
## Known issues
336-
337-
### nanoSQL2
338-
339-
If your application depends on [nanoSQL 2](https://www.npmjs.com/package/@nano-sql/adapter-sqlite-nativescript) for data persistence, you should check which database is in use (and change it, if applicable) before running a query against your database. You can do it as follows:
340-
341-
```ts
342-
if (nSQL().selectedDB !== dbName) {
343-
nSQL().useDatabase(dbName);
344-
}
345-
nSQL(tableName).query(...);
346-
```
347-
348335
## Plugin authors
349336

350337
<a href="https://github.com/agonper" title="Alberto González Pérez">

0 commit comments

Comments
 (0)