Obsolete
Status Update
Comments
ar...@google.com <ar...@google.com>
ar...@google.com <ar...@google.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).
wq...@gmail.com <wq...@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).
is...@google.com <is...@google.com>
ar...@google.com <ar...@google.com>
sa...@google.com <sa...@google.com> #4
I totally agree that this should be implemented as an index. It could (and I think
should) still be specified in the schema/property constructor and the index
automatically generated.
should) still be specified in the schema/property constructor and the index
automatically generated.
Description
Version used:26.1.0
Theme used: Theme.AppCompat.Light.DarkActionBar
Devices/Android versions reproduced on: Emulator with Android O
- Relevant code to trigger the issue.
//create your notification channel
val notification = NotificationCompat.Builder(this, CHANNEL_ID)
.setSmallIcon(R.mipmap.ic_launcher)
.build()
notificationManager.notify(NOTIFICATION_ID, notification)
Simple code as that. And it will crash App even without a stacktrace in Logcat. It works fine with API level 25 and probably under that Level. But in Android O it just crashed. Even more, I can't even unlock my Phone.
I asume it could be a Bug for Android O other than support-lib.
- A screenrecord or screenshots showing the issue (if UI related).