-
Notifications
You must be signed in to change notification settings - Fork 67
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
[help] CouchDb 3.0 - Partitioned Databases #123
Comments
Not yet. But we are updating |
thx. |
Has this been added yet? If not, then why was this issue closed? |
Opening again because this seems like a good thing to support. Because Does anybody know if there is a data migration tool for this already? I also think we should look closely at polymorphism and partitioning, to not miss, if possible, to improve on polymorphism partitions. |
@broerse sorry for close the issue. I'm prefixing my ids in order to use partitioned types at the couch/server and use relational-pouch at the browser/client. COUCH_ID_PREFIX=: import { v4 as uuid } from 'uuid'
export default {
async demo (db) {
const id = process.env.COUCH_ID_PREFIX + uuid()
await db.rel.save('post', {
title: 'Rails is Unagi',
text: 'Delicious unagi. Mmmmmm.',
id: id
})
const { posts: [ post ] } = await db.rel.get('post', id)
}
} but that is only a workaround, and a workaround is never a good thing, i'll remove that as soon u guys come with something. |
is there any way to config the format of the ids? currently:
<type>_<id type>_<id>
I want to use
<type>_<id type>:<id>
instead of<type>_<id type>_<id>
to take advantage on the new Partitioned DatabasesCurrently, as a workaround, I'm prefixing all my ids with
:
The text was updated successfully, but these errors were encountered: