5 stars based on
Initially there were too many bugs in Safari's implementation for PouchDB to use it however after a lot of work from the WebKit devs and a few releases IndexedDB support became 6345 the readasbinarystring methods in Safari and as of this release is now the default storage engine for PouchDB in Safari.
Switching to IndexedDB vastly reduces the amount of work we need to do to keep PouchDB stable, any new features and improvements relating to storage up 6345 the readasbinarystring methods now has meant duplicating the entire code and effort for WebSQL, we will also see a nice reduction in the bundle size. If you are using PouchDB and expect to want to use new releases then you will need to migrate your current users, this release of PouchDB supports both WebSQL and IndexedDB in Safari so one solution that may work depending on your circumstances is to replicate between them like so:.
With PouchDB we aim to keep breaking changes to a minimum which means when we do have a breaking change release like the upcoming 7. These arent all certain and 6345 the readasbinarystring methods can follow along or join in with the 7. As always, we welcome feedback from the community and would love to hear what you think of this release as well as PouchDB's future direction.
Please don't hesitate to file issues or get in touch. And of course, a big thanks to all of our new and existing contributors! I'm happy to announce the release of PouchDB 6. For a full changelog from 6. Some of the highlights:. This seen a huge 8X speedup in Chrome and 2X in Firefox.
JS to ensure they use a cookie jar. Makes minor perf improvements and fixes some inefficiencies in packaging, also PouchDB can now be Rollup'ed itself. This release brings early retirement to those features that have done great work over the years, but whose services are no longer necessary don't worry, we will pay their pensions in full. Along with the removed features, we have a large list of bugfixes, 6345 the readasbinarystring methods work and general improvements for you to enjoy with your BBQ.
The constructor is now stateless. If you need to test whether setup can complete, then new PouchDB dbName. Note this also applies to the callback style, i. Please use the pouchdb-adapter-cordova-sqlite plugin instead.
Instead these have been extracted out into separate packages:. Please see Custom builds for more info. Instead of the getUrl API, you can use db. For getHeaders no replacement is intended. Both APIs were previously undocumented. Instead, websql is removed entirely use pouchdb-adapter-node-websql insteadand leveldown is now required. If you want 6345 the readasbinarystring methods avoid installing leveldownthen you can use the pouchdb-browser preset if you don't need Node support, or you can use pouchdb-memory if you only need an in-memory database.
For all other uses, see Custom builds. View and filter functions now execute in 'use strict' environments and within a sandbox in Node. Please read carefully in case you are using any of these features. We have removed the PouchDB.
These were always undocumented and unsupported, and we regret if anybody accidentally 6345 the readasbinarystring methods up relying on them. Instead of using this format which has been undocumented and unrecommended for some 6345 the readasbinarystring methodsplease do:. There is no need to "wait" for the PouchDB constructor to asynchronously finish setting up, since the constructor has been made stateless.
However, if you really want to verify that the database is ready and working, you can do an info request. This may be interpreted as a breaking 6345 the readasbinarystring methods, if you are already using the node-websql adapter in production and have saved your data somewhere, within the span of time between 5.
Unlikely, hence the patch change. If so, you can migrate by simply doing:. This currently only covers 6345 the readasbinarystring methods. We have had issues in the past with how to manage npm dependencies.
Version ranges can lead to other people breaking PouchDB with their releases, and strict versions lead to us using stagnant packages and not being aware of upcoming breakages.
During this month, the hood. Please file issues or tell us what you think. And as always, a big thanks to all of our new and existing contributors! Having a destroy function on the PouchDB object was always a little awkward, which is why we introduced the db.
So now that PouchDB. Keep in mind that the PouchDB object is no longer usable after you destroy it. So you should call new PouchDB 6345 the readasbinarystring methods if you want to re-use it. These events 'create''update'and 'delete' were intended to make the changes API 6345 the readasbinarystring methods to work with, but they ended up being too ambitious and confusing, so 5.
Keep in mind that this "update vs. Most 6345 the readasbinarystring methods the time, your UI should be able to handle document "updates" or "creates" equivalently, so change. This was an alternative IndexedDB adapter based on Level.
It is exactly the same as 4. When discussing what features we should add, we should also discuss what to remove. I can't remember or find the exact quote, but it was something along those lines. We try to maintain backwards compatibility as much as 6345 the readasbinarystring methods with PouchDB, however sometimes we need to let go of those features that just didn't work out like planned. We have previously marked quite a few things as deprecated, and in this 4.
6345 the readasbinarystring methods previously used bluebird as our Promise polyfill in node. However bluebird contains a lot of non-standard Promise functionality, which authors could use and then have their code break in browsers as well as iojs and future versions of node.
PouchDB will always use the globally available Promise object where available, so if you have 6345 the readasbinarystring methods used standard Promise functionality, this change will not break anything. If you require the extra functionality provided by bluebird6345 the readasbinarystring methods you can have PouchDB use it with. These callbacks have long been replaced with the EventEmitter -style changesreplicate and sync APIs, and are finally being removed.
If you still have:. It has since been replaced by the paused event, which will do the same and additionally indicate whether the replication was paused due 6345 the readasbinarystring methods an error. It also contains one minor new feature. Do you support better documentation for PouchDB users?
If so, then today you should cast your vote in support of PouchDB. Together, we can make a better future release of PouchDB. However regularly scheduled programming has resumed and today I am happy to announce PouchDB 3. Over the last 2 months a huge amount of work has gone into PouchDB's documentation including which allows you to switch between a Promises and a callback format for your code examples.
We have hugely expanded the coverage of the documentation so if there is anything missing please feel free to point it out. This is a quick release, ahead of our normal monthly release schedule, to fix some critical bugs and ship them out sooner to our eager PouchDB fanbase.
We have introduced new events to give you more information what is happening during syncing. There are now active and paused events triggered during replication and the uptodate event is now deprecated. Calvin did 6345 the readasbinarystring methods base work for this a long 6345 the readasbinarystring methods ago, however we now officially support a retry option to replication. If you do a db. A lot of developers wanted to know what documents were being referred to when they recieved a change event.
Today marks the dawn of a new PouchDB release, 3. Here are some of the highlights:. This release includes a migration. Your existing database will be updated automatically, but you cannot downgrade to a previous version of PouchDB once you've upgraded.
They cover a lot of the issues surrounding building PouchDB applications including conflicts and promises vs callbacks. As a bonus the guides as well as the rest of the website now work offline. If you have been using attachments in your PouchDB databases, you may have noticed that it was a bit bigger round the waist than it should have been. We now work harder to ensure there isnt any extra things lying around the database taking up space that you no longer need.
This change came along with a lot of compaction and attachment related fixes: There is a big change brewing in CouchDB world, https: This will represent a big change towards CouchDB however there is no need to worry, we now run all of our tests against the current master CouchDB and they are all green!
We keep a list of plugins and related external projects to PouchDB, here are a few new ones we added during this month:. We would also like to give a huge thanks to our new and existing contributors. This release contains a workaround for some unforeseen hiccups in Apple's new implementation of IndexedDB for Safari 7. All joking aside, we are happy to welcome Apple to the IndexedDB party better late than never!
In the meantime, PouchDB 3. Tonight our fine dining selection is PouchDB 3. You can now call PouchDB. You can now have as many revisions to your documents as you want, and you'll no longer descend Inception -style into a "too much recursion" or "maximum call stack" error. We literally wrote a custom JSON parser 6345 the readasbinarystring methods fix this.
That's how much we love you. This week we present PouchDB 3.