Closed GoogleCodeExporter closed 9 years ago
I agree objects should be dirty when created. Currently they are only saved when
their properties get modified
Original comment by amle...@gmail.com
on 10 Feb 2009 at 12:54
This seems to have been addressed in rev64, but I think that it's a bit wrong
now that there's a property called
'dirty' as that means all tables end up having a 'dirty' column which is always
0. It also means that you can't ever
have a real property of an SQLitePersistentObject being called 'dirty'.
Original comment by mattjgal...@gmail.com
on 15 Feb 2009 at 10:51
[deleted comment]
Original comment by amle...@gmail.com
on 17 Feb 2009 at 11:40
Original issue reported on code.google.com by
baron.ro...@gmail.com
on 8 Feb 2009 at 4:37