These are some of the features that have been added since the first release.

---

DefaultCommandType

1. DefaultCommandType allows for setting the method by which the EasyObject will conduct database operations. There are two settings: CommandType.StoredProcedure and CommandType.Text.
2. CommandType.StoredProcedure instructs the EasyObject to use stored procedures. CommandType.Text instructs the EasyObject to generate dynamic SQL. 
3. The DefaultCommandType can be set in the concrete class's constructor, so it becomes the default for that object.
4. The Save method also has an overload that takes a CommandType, which will override the DefaultCommandType (but only for the Save operation).
5. All database operations will execute within the current transaction scope, regardless of the CommandType setting.

Products prod = new Products(); prod.DefaultCommandType = System.Data.CommandType.StoredProcedure; // Call AddNew() to add a new row to the EasyObject. You must fill in all // required fields or an error will result when you call Save(). prod.AddNew(); // Note the use of the 's_' fields, which take strings as arguments. If this object // were being loaded from TextBox objects on a WinForm, you don't have to worry about // the datatype because this is handled for you in EasyObjects prod.s_ProductName = "EasyObjects"; prod.s_Discontinued = "True"; prod.s_QuantityPerUnit = "10"; prod.s_ReorderLevel = "100"; prod.s_UnitPrice = "49.95"; prod.s_UnitsInStock = "200"; // Override the DefaultCommandType prod.Save(System.Data.CommandType.Text);

---

IDENTITY Insert

1. Allows the developer to specify a value for a column marked in the database as IDENTITY (in SQL Server) or using a SEQUENCE (in Oracle, which is support by EasyObjects).
2. Typically used when transferring data from one database to another, or when adding static lookup data. 
3. Always performed with a dynamic query, no stored procedure support at this time.

Products prod = new Products(); // Call AddNew() to add a new row to the EasyObject. You must fill in all // required fields or an error will result when you call Save(). prod.AddNew(); // We're going to provide our own IDENTITY column for this record // NOTE: IDENTITY insert is always done with a dynamic query prod.IdentityInsert = true; // Note the use of the 's_' fields, which take strings as arguments. If this object // were being loaded from TextBox objects on a WinForm, you don't have to worry about // the datatype because this is handled for you in EasyObjects prod.s_ProductID = "78"; // <-- Predefined ID prod.s_ProductName = "EasyObjects"; prod.s_Discontinued = "True"; prod.s_QuantityPerUnit = "10"; prod.s_ReorderLevel = "100"; prod.s_UnitPrice = "49.95"; prod.s_UnitsInStock = "200"; // Save to the database prod.Save();

---

Aggregates

1. Allows the developer to construct dynamic queries that contain aggregate functions.
2. Supported functions are AVG, COUNT, MAX, MIN, SUM, STDEV and VAR, but can vary by database provider.

Products prod = new Products(); // Query for the average UnitPrice prod.Aggregate.UnitPrice.Function = AggregateParameter.Func.Avg; prod.Aggregate.UnitPrice.Alias = "AveragePrice"; prod.Query.Load(); // Use GetColumn because AveragePrice is not part of the schema return (decimal)prod.GetColumn("AveragePrice");