by Matthew Noonan
23. October 2006 18:28
I don't know why it didn't occur to me, but I developed a plan on how to do default value handling (client-side) in EasyObjects, and I forgot to include it in the 1.2 release. So, as of today, I will add this feature (if the approach remains feasible and maintainable) to EO 1.2. I won't go into technical details just yet, but the basic plan is to recognize certain common SQL functions (such as GetDate(), sysdate, NewID(), etc.) and to recognize numeric defaults. Anything else will be treated as a string value, which will negate the use of custom functions and other errata that would cause the EO code to break. The "ApplyDefaults" method will be overridable, so if you have some custom function, you will have to override the generated defaults and add your own client-side code.
I know server-side default processing has been requested, but EO will have to undergo a nearly-complete rewrite in order to accomplish this, and obviously that's just too big a task for this release. Client-side defaults will at least allow for displaying the values in a new grid row. We'll get to server-side defaults in EO3.
I welcome your comments on this issue.
by Matthew Noonan
23. October 2006 00:22
It's been a long time coming, but NCI is pleased to announce the availability of the EasyObjects.NET 1.2 Release Candidate. While this version only supports .NET 1.1 and the June 2005 Enterprise Library, the features will be ported forward into the upcoming 2.0 version. If you find any problems with this release, please contact the support staff immediately so that we may correct it before final release.
Thanks for choosing EasyObjects as your development platform!
Change log for EO 1.2:
Click here to download EasyObjects 1.2 Release Candidate
by Matthew Noonan
19. October 2006 05:49
Wow, I have just checked in to Tigris a bunch of NUnit tests for EO 1.2. I discovered a few bugs, as well as some inconsistancies between the C# and VB templates. Those Agile/TDD folks might be on to something there... 
That takes care of C# and VB on SQL Server, tomorrow night I will get started on the Oracle tests.
by Matthew Noonan
16. October 2006 03:10
I just checked in some changes to the Tigris source tree that will be released in EO 1.2 (C# and SQL Server only, for the moment).
- IDENTITY insert - for those times when you need to override the autokey generation. This feature is usually used when migrating data from one schema to another.
- Better timestamp handling - handling timestamps for SQL 2000 vs. SQL 2005, and the concurrency was not functioning properly with dynamic queries.
- Sql2005DynamicQuery class - to support the new timestamp handling.
I have heard occasional complaints about being unable to download the source code from Tigris, so if you are having trouble please let me know.
Subscribe