Timeline for 'Better' way to handle adding a record
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Feb 14, 2014 at 6:40 | comment | added | Aron | I agree on the catch, it is better to have your exceptions bubble up to the UI layer and have the UI layer display the exception. In fact, I would in the Data Layer wrap expected exceptions, then have the UI display the exception (knowing that you have no write permissions is much nicer than , "ERROR"). Also, NEVER use a string when an Enum can do the job. Finally, I would write bulk insert methods, as your code will do 3/4 queries over 2 or so round trips per insert. | |
| Feb 13, 2014 at 20:23 | history | edited | Simon Forsberg | CC BY-SA 3.0 |
added 145 characters in body
|
| Feb 13, 2014 at 18:46 | history | edited | Simon Forsberg | CC BY-SA 3.0 |
added 315 characters in body
|
| Feb 13, 2014 at 18:29 | history | answered | Simon Forsberg | CC BY-SA 3.0 |