Update of /cvsroot/webware/Webware/MiddleKit/Docs
In directory sc8-pr-cvs1:/tmp/cvs-serv2613/Docs
- move MSSQL's decimal support up to the SQL level
- use keys Precision and Scale
- add to testing
RCS file: /cvsroot/webware/Webware/MiddleKit/Docs/RelNotes-0.8.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** RelNotes-0.8.html 10 Nov 2002 10:43:23 -0000 1.4
--- RelNotes-0.8.html 15 Jan 2003 00:02:31 -0000 1.5
*** 45,48 ****
--- 45,51 ----
<li> Also, the database name can be passed via the constructor. See the <a href=UsersGuide.html#MT_DatabaseName>User's Guide</a> for more info.
+ <li> Support for the SQL 'decimal' type, previously found only in the MSSQL adapter, has been brought up to the generic SQL adapter level which means that MySQL inherits it. Use the attribute keys <span class=name>Precision</span> and <span class=name>Scale</span> to specify the precision and scale just like you see in SQL manuals: decimal(precision, scale).
+ <p> If (and only if!) you have "legacy" code from the old decimal support, you could enable the <span class=name>UseMaxForDecimalPrecision</span> setting. However, you might get fried down the road when MiddleKit starts enforcing min/max constraints on decimal types. (Getting fried implies you would have to edit/fix your model.)
<p> "Dangling obj refs" now print much more useful information. The old message:
RCS file: /cvsroot/webware/Webware/MiddleKit/Docs/TODO-MiddleKit.text,v
retrieving revision 1.32
retrieving revision 1.33
diff -C2 -d -r1.32 -r1.33
*** TODO-MiddleKit.text 26 Oct 2002 07:41:42 -0000 1.32
--- TODO-MiddleKit.text 15 Jan 2003 00:02:31 -0000 1.33
*** 284,287 ****
--- 284,289 ----
[ ] A potential optimization to help speed start up would be to pickle the Model inside the .mkmodel directory and use that pickle file in place of the .csv (provided the .csv mtime was older). We could do this silently similar to .pyc files. Note that the only speed up here is in start up time.
+ [ ] It would make more sense if the Float type spewed a SQL decimal type in response to having "precision" and "scale" attributes. Then axe DecimalAttr (or at least deprecate it).