Obsolete
Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
As a corollary, for properties where unique=True one
should be able to fetch an entity by doing
Model.get_by_uniquepropertyname and also
Model.get_or_insert_by_uniquepropertyname... like Rails does with
ActiveRecord (e.g., Book.find_or_create_by_isbn).
should be able to fetch an entity by doing
Model.get_by_uniquepropertyname and also
Model.get_or_insert_by_uniquepropertyname... like Rails does with
ActiveRecord (e.g., Book.find_or_create_by_isbn).
en...@google.com <en...@google.com>
li...@gmail.com <li...@gmail.com> #3
I'd rather see this added as an index feature, so the uniqueness could be spread
across multiple fields (and an index would almost certainly be needed to support this
efficiently, anyway).
across multiple fields (and an index would almost certainly be needed to support this
efficiently, anyway).
Description
The JavaScript code in question is:
var type = navigator.connection.type;
console.log(type); // always 0
This bug is seen in Android 2.2 and 2.3. The navigator.connection object was added in Android 2.2 and works just fine in the Web Browser that comes with Android.