Mapper was trying to get generated keys based on primary keys, not fields marked autogenerated
Updated 2 years, 1 month ago
| Derek Chen-Becker | Reviewers | ||
| 13, 231 | dchenbecker, dpp, marius, charles, heiko, joni, atsuhiko, jorge, naftoli, kris, indrajit, alexb | ||
| None | LiftWeb-archive | ||
This came up while working on issue 13. Basically, a non-DB-generated PK (MappedStringIndex) was being used and Mapper was trying to retrieve the generated value from the db anyway. The new fix finds generated fields based on the dbAutogenerated_? property instead of dbPrimaryKey_?.
On the app submitted for issue 13 as well as my own test app.
Review request changed
Updated 2 years, 1 month ago (December 8th, 2009, 11:03 a.m.)
-
On the app submitted for issue #26 as well as my own test app.
On the app submitted for issue 13 as well as my own test app.
-
This came up while working on issue #26. Basically, a non-DB-generated PK (MappedStringIndex) was being used and Mapper was trying to retrieve the generated value from the db anyway. The new fix finds generated fields based on the dbAutogenerated_? property instead of dbPrimaryKey_?.
This came up while working on issue 13. Basically, a non-DB-generated PK (MappedStringIndex) was being used and Mapper was trying to retrieve the generated value from the db anyway. The new fix finds generated fields based on the dbAutogenerated_? property instead of dbPrimaryKey_?.
-
- added 13
Fixed markup formatting for the related issue