EasyObjects.NET 1.1 Released!

[mgnoonan]

New features and bug fixes:

• Complete functionality without generating stored procedures. You no longer have to generate stored procedures for your business objects (although this is still supported). You now have the option. This paves the way for adding support for database platforms that do not support stored procedures (Access, VistaDB, MySql, SqlLite, etc.).
• Support for Aggregate functions in custom queries, courtesy of David Neal Parsons.
• Ability to load an EasyObject from a DataTable or a DataSet (specifying the index of the DataTable). This allows for developers to return multiple resultsets from a stored procedure and then load the objecct from the DataSet.
• Updated the QuickStart to prompt for dynamic connection information, including the server name and user credentials.
• Fixed a bug where the internal datatable was not removed from the dataset when an exception occurred (reported by daveyjclark).
• A small set of NUnit tests are now included.
• Some minor enhancements.

Blog entry:
http://www.easyobjects.net/Blog/tabid/124/EntryID/17/Default.aspx

Download it today!
http://www.easyobjects.net/Downloads/tabid/125/Default.aspx

[TimGSXR]

hi mark,

all sounds very good, was wondering if the sql default values bug has been fixed yet?

[mgnoonan]

Not yet, but I actually have a line on how to fix it. Keep an eye on the blog, as I probably will not do a full release on it, just an update to the templates.

http://www.easyobjects.net/Blog/tabid/124/Default.aspx

[VincePlatt]

New features and bug fixes:

• Complete functionality without generating stored procedures. You no longer have to generate stored procedures for your business objects (although this is still supported). You now have the option. This paves the way for adding support for database platforms that do not support stored procedures (Access, VistaDB, MySql, SqlLite, etc.).

Matt, is there any documentation on how to use this feature? I think it has something to do with the Build*Query methods, is that right?

[mgnoonan]

Yeah, um, documentation...

I'm afraid this response will have to do for now (weekend warrior, you know). All you have to do is set the DefaultCommandType property on your object to either CommandType.Text (for dynamic queries) or CommandType.StoredProcedure.

If you always plan to use dynamic queries, my advice is to set the DefaultCommandType in the constructor (Sub New in VB) of the concrete class. Alternatively, you can call Save() with the CommandType of your choice.

That is all you have to do, no other action is required on your part.

I have toyed with the idea of changing the default from stored procedures to dynamic queries, but I have not heard any feedback either way on this topic.

[VincePlatt]

No need to feel bad about documentation; been there, done that.

Anyway, I will have to try out your answer tomorrow. If that's all it takes, then let me just say it right now:

THANK YOU, THANK YOU, THANK YOU!!! FERTHELUVOFGAWD THANK YOU!

Heh...

I was thinking I would have to re-write some significant portion of the EasyObjects template to do this (and I'm on a VERY tight schedule so you can imagine my relief). Now if the Oracle DBAs on this project turn their collective noses up on those stored procedures because they don't meet some esoteric naming standard I'll just party on.

BTW - On the subject of documentation, I may have missed something, but since IsAutoKey always comes back as false for Oracle PKs (even when there is an assigned sequence), I had to dig pretty hard to find that SEQ:I:sequence_name trick. I assume that the sequence calls will still work with the dynamic SQL calls right? I'll just have to try that tomorrow.

Thanks again and take care,
-Vince

[TimGSXR]

I was wondering about this the other day. Stored procedures are obviously meant to improve performance so I thought I'd go for dynamic during dev then on release produce all the stored procedures and switch. I'm going to switch to dynamic today so I'll post back or even postback, haha, .

[mgnoonan]

Yes, the SEQ stuff should work with dynamic queries. I spent a lot of time trying to get that to work, it was not an easy or straightforward solution (nothing on Oracle ever is, it seems). I even had to get some help from the big guns (a.k.a. Mike).

So let me know if you encounter any problems.

[nead]

What is the SEQ stuff about? Are you referring to SEQUENCE in oracle?

I am looking for some ways to change the template so that STORED procedures generated can use Oracle SEQUENCE to generate new PK for new records insertion.
At the moment, I change each STORED PROCEDURES manually in Oracle, menial but at least it works

[mgnoonan]

Are you using the EasyObjects Oracle Stored Procedure template? That's all built in there for you...

[nead]

Kindly refer to the new thread created http://www.mygenerationsoftware.com/phpbb3/viewtopic.php?p=9431#9431