<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hot on the heels of 1.3.0, i am hoping to release 1.3.1 next week.<div><br></div><div>Here is a list of the JIRA's associated with it</div><div><br></div><div><a href="https://issues.jboss.org/issues/?jql=project%20=%20AGJS%20AND%20fixVersion%20=%20%221.3.1%22%20ORDER%20BY%20updated%20DESC,%20priority%20DESC,%20created%20ASC">https://issues.jboss.org/issues/?jql=project%20%3D%20AGJS%20AND%20fixVersion%20%3D%20%221.3.1%22%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC</a></div><div><br></div><div>There was some bug fixes and test/documentation updates, but there were 2 big option added in DataManager:</div><div><br></div><div>1. Auto Connect</div><div><br></div><div>Since IndexedDB and WebSQL needed to both be "opened" before doing a read/save/remove/filter , i've added an option " auto" to the creation of a store. It will default to false, so it will not break any existing stuff. if set to true, then you can do the a read, for example and not have to worry about calling open.</div><div><br></div><div>2. Opt-Out of Fallback and "preferred"</div><div><br></div><div>this new option, 'fallback' will default to true, so data manager will fallback to a support adapter by default, but if you want to make sure an error is thrown if an adapter is not supported then you can set fallback=false.</div><div><br></div><div>there is also a new "preferred" option. By default when fallback is enabled, this is the order the adapters are tried [ "IndexedDB", "WebSQL", "SessionLocal", "Memory" ]</div><div><br></div><div>now a user can specify a list of adapters they want to try, so they can do [ "Memory" ] if they only want to fallback to the memory adapter if lets say IndexedDB isn't available</div><div><br></div><div><br></div><div><br></div><div>So give it a try</div><div><br></div><div><br></div></body></html>