Hi @pubkey, after calling database.remove(), all IndexDB databases are removed except for one called "_pouch_documentdb-rxdb-0-documents-local", which seems to hold some information about the latest pullDocument/pushSequence. Is this intentional? Now when a user logs out, I do
await (await getDatabase()).remove();
(await indexedDB.databases())
.filter(({ name }) => name.startsWith('_pouch'))
.map(({ name }) => indexedDB.deleteDatabase(name));
This seems to do the trick to let the documents repopulate when a user logs back in and the database is recreated. Is there something more natural that we ought to be doing to actually delete all the databases, instead of all-but-one? Or is there some alternative set of steps that ought to be done when we want to remove user-data from the browser due to the user logging out?
@plmercereau see above for my more heavy-handed method for dealing with the lingering last-pulled-document info. I'm curious to know what reasoning there is behind leaving that one database remaining, but without that info, just deleting the whole thing feels like the best move
I'm having a mysterious issue that I'm hoping someone can help me with. Whenever I
remove() and then recreate a collection, operations on that collection seem to work but also give me an error saying Error: primary missing !!. I'm noticing one other issue that I assume is related, which is that an observation on a query of that collection, does not have its initial execution called.
Both of these things work fine the first time I create the collection: operations on the collection run without an error, and the initial instance of an observation query is successfully run.
RxError (COL19): RxError (COL19)
what are these error for
@pubkey re my
Error: primary missing !! issue -- I went into my node_modules and added console.log(change) to addEventToChangeStream in rx-storage-pouchdb. I'm seeing that when I add a collection, remove it, and then add it again (a collection of the same name), addEventToChangeStream gets run twice whenever I e.g. insert a document. The change dict in both instances of a single insert call are identical except that the first one shows a doc.collectionName property set to undefined. I take this to mean that there's some sort of rxjs observation that continues to occur for a collection that has been removed, which is causing problems. I've been looking through rx-database to try and see where observations are initiated and perhaps removed, but haven't been able to figure that out yet. Any hints on how to continue appreciated.
Hi @pubkey, can you give some kind of clue on the mechanism that's involved here, to help me figure out how to make a test case? Can you let me know if you agree with my interpretation of what I'm observing, namely "I take this to mean that there's some sort of rxjs observation that continues to occur for a collection that has been removed, which is causing problems." And if so, should I be able to observe something about whether there are rxjs observations persisting when they shouldn't, by looking at the destroyed collection (e.g.
collection.$)
I'm using graphql replication, but I've disabled replication while I'm trying to figure this out. I.e. the problem still happens with no replication
^ in case it's useful
@pubkey In the process of doing all the things in the checklist, I noticed that the problem (mysteriously) goes away simply in virtue of having
import { PouchDB } from 'rxdb';. Even if I don't then reference PouchDB. Why is that fixing this?
this does not make sense to me
which bundler do you use?
I have no idea what this could be
import { RxDBValidatePlugin } from 'rxdb/plugins/validate';
import { addRxPlugin, createRxDatabase } from 'rxdb/plugins/core';
import { addPouchPlugin, getRxStoragePouch } from 'rxdb/plugins/pouchdb';
import {
RxDBReplicationGraphQLPlugin,
pullQueryBuilderFromRxSchema,
pushQueryBuilderFromRxSchema,
graphQLSchemaFromRxSchema,
} from 'rxdb/plugins/replication-graphql';
import idb from 'pouchdb-adapter-idb';
as soon as you import from the rxdb default, you automatically import all plugins
so it looks like this starts any sideEffect which should not change anything
but it does
Okay so what I was observing was that the error message stopped happening ... but also other things were not quite right, like observed queries were not working. Figured out I need to import PouchDB before everything else - now I get the error, but things are otherwise working.
I've done all the steps of the debug checklist except for the memory plugin, which I'll do now
Also I'm not seeing anything useful in the pouchdb debug messages
Can you let me know if you agree with my interpretation of what I'm observing, namely "I take this to mean that there's some sort of rxjs observation that continues to occur for a collection that has been removed, which is causing problems." And if so, should I be able to observe something about whether there are rxjs observations persisting when they shouldn't, by looking at the destroyed collection (e.g. collection.$)
Hey there, I am facing an issue with adding collection and data. Here's the createRxDatabase:
const db: RxDatabase = await createRxDatabase({
name: './data/server-db',
storage: getRxStoragePouch('websql'),
ignoreDuplicate: true,
});
then I add a collection with
await db.addCollections({
items: {
schema: mySchema
}
});
and add insert an document with:
await db.items.upsert(....);
But there seems to be a problem that the collection will not be properly created. I cannot browse the collection by http://localhost/db/items. It says "no_db_file". Any ideas? Your help is highly appreciated.
Using:
const db: RxDatabase = await createRxDatabase({
name: 'db',
storage: getRxStoragePouch('websql'),
it will work. Seems to be still the issue with the subfolder in the name under typescript. See: https://github.com/snookyly/rxdb-filefolder
const db: RxDatabase = await createRxDatabase({
name: 'db',
storage: getRxStoragePouch('websql'),
it will work. Seems to be still the issue with the subfolder in the name under typescript. See: https://github.com/snookyly/rxdb-filefolder
@ebukaodini Just invert the colours: https://chrome.google.com/webstore/detail/high-contrast/djcfdncoelnlbldjfhinnjlhdjlikmph?hl=da