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
Currently, when creating a collection the following logic determines the name of the database:
database.prefix + ':RxDB:' + name
This causes a problem when trying to use RxDB with CouchDB, since both uppercase letters and colons are illegal characters for a CouchDB database name.
An example of my use case, when trying to connect to a CouchDB host:
{
"error": "illegal_database_name",
"reason": "Name: 'db_name:RxDB:col_name'. Only lowercase characters (a-z), digits (0-9), and any of the characters _, $, (, ), +, -, and / are allowed. Must begin with a letter."
}
The solution here is simple, we can change :RxDB: to -rxdb-, but this will probably cause much damage to those who are already using the library.
Or am I misusing the library? :)
The text was updated successfully, but these errors were encountered:
iMoses
changed the title
Stay CouchDB-compliant, as PouchDB
Stay CouchDB-compliant
Jan 31, 2017
Hi @iMoses
There are currently no tests for the usage of the http-adapter. Therefore I didn't detect that it won't work.
I will add the tests in the near future.
Since we use semver, we can update the library without breaking existing systems.
I will switch RxDB to version 3.x when the branch schemaMigration is ready.
At this time I can change the prefix and also add some checks so it throws when people use an invalid collection-name.
Currently, when creating a collection the following logic determines the name of the database:
database.prefix + ':RxDB:' + name
This causes a problem when trying to use RxDB with CouchDB, since both uppercase letters and colons are illegal characters for a CouchDB database name.
An example of my use case, when trying to connect to a CouchDB host:
Receives the following response:
The solution here is simple, we can change
:RxDB:
to-rxdb-
, but this will probably cause much damage to those who are already using the library.Or am I misusing the library? :)
The text was updated successfully, but these errors were encountered: