Open GoogleCodeExporter opened 9 years ago
Clarified summary: DataSources in general can reject colliding primaryKeys
through normal SmartGWT error handling, although we recommend that the UI is
constructed so that this error condition never occurs.
This issue points out that a client-only DataSource, which is basically a
simulator of a remote DataSource, does not report such collisions - it may as
well do so but priority is very low, especially given that you usually want to
avoid this entirely.
Original comment by smartgwt...@gmail.com
on 2 Apr 2012 at 6:10
The UI I am designing gives the user the possibility to add new rows into a
ListGrid populated by a DataSource. This is why I require the PrimaryKey to
work in order to prevent the user from adding duplicate rows.
Will this be fixed soon?
Original comment by sta191...@gmail.com
on 2 Apr 2012 at 6:43
You can catch this error condition yourself by using fetchData() to detect
duplicates, or by using a DataSource that actually makes contact with the
server.
So again, very low priority, will not be fixed soon unless a customer with
support happens to ask for it.
Original comment by smartgwt...@gmail.com
on 2 Apr 2012 at 6:53
Sorry to bother you again but on what event should I perform the fetchData().
Is it the addEditCompleteHandler or something else?
Original comment by sta191...@gmail.com
on 2 Apr 2012 at 7:00
Original issue reported on code.google.com by
sta191...@gmail.com
on 2 Apr 2012 at 3:35