Changes between Version 197 and Version 198 of BackwardsIncompatibleChanges
- Timestamp:
- Jul 30, 2008, 10:56:00 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BackwardsIncompatibleChanges
v197 v198 69 69 * [7971] July 18, 2008 [#Movednewformstoforms Moved django.newforms to django.forms] 70 70 * [8015] July 19, 2008 [#ChangedthewayURLpathsaredetermined Changed the way URL paths are determined] 71 * [8143] July 30, 2008 [#DecimalFieldconversiontightened DecimalField conversion tightened] 71 72 72 73 == Database constraint names changed == … … 1039 1040 number of solutions that works for all web servers, rather than have to include 1040 1041 25 special cases for each webserver and installation possibility). 1042 1043 == !DecimalField conversion tightened == 1044 1045 In [8143] the conversion between values in model attributes and values to be inserted into the database was changed internally. A side-effect of this is that Django will raise an error if you try to store a floating point value in a !DecimalField. There is no reliable way to convert between a float and a decimal. So you must either store a python `decimal` value in the model attribute or a string (which will then be converted to a `decimal`).