EntitySpaces 1.4.2
We have accumulated enough fixed and tested issues that we thought it was important to put out a maintenance release. The new downloads should be posted on Friday, August 4, 2006. We will announce their availability in the forums, once they are up. The following issues are addressed in this version:
- Change Guid with default newid() to accept input for Saves for Microsoft SQL Server.
- Add XML comment to LoadByPrimaryKey that warns if the template is run on a table with no primary key.
- Trim invalid characters from aliases in esPlugin.
- Add preliminary LINQ support.
- AddNew rolls back for MySQL provider without error with InnoDb tables.
- Error in MySQL stored procedure template comment if all fields are in the primary key.
- IndexOutOfRangeException if the primary key(s) is(are) not the first column(s) in a table.
- ASPX page template ignores Namespace.
- Adding fks broke WebServices' serialization.
- Do not over-write files when generating Custom Master classes.
- Add using System.ComponentModel when not generating a single file.
- Multi-line default values not generated correctly.
- Remove Query.Load("OR") from compiled help and document Query.es.DefaultConjunction instead.
The default conjunction for Query.Load() is "AND". You can change that with this: emps.Query.es.DefaultConjunction = esConjunction.Or;
- Add QueryReset to Entities and EntityCollections.
TestCollection collection = new TestCollection();
// Get the LastName for active employees
collection.Query.Select(collection.Query.LastName);
collection.Query.Where(collection.Query.IsActive == true);
collection.Query.Load();
Assert.AreEqual(16, collection.Count);
// These get added to the above.
// Now we get LastName, FirstName
// For active employees named "Costner"
collection.Query.Select(collection.Query.FirstName);
collection.Query.Where(collection.Query.LastName == "Costner");
collection.Query.Load();
Assert.AreEqual(3, collection.Count);
// Reset the query and return all columns and all rows
collection.QueryReset();
collection.Query.Load();
Assert.AreEqual(30, collection.Count);
- Add Scale and Precision to esParameter for output parameters.
public partial class AggregateTestCollection : esAggregateTestCollection
{
public void TestParamsWithScale()
{
esParameter myParam = new esParameter("Salary", 12.34);
myParam.DbType = DbType.Decimal;
myParam.Precision = 18;
myParam.Scale = 2;
myParam.Direction = esParameterDirection.Output;
esParameters parms = new esParameters();
parms.Add(myParam);
parms.Add("FirstName", "Entity");
parms.Add("LastName", "Spaces");
this.ExecuteNonExec(esQueryType.StoredProcedure, "proc_esTestInsert", parms);
}
}
EntitySpaces 1.5
We have rescheduled the 1.5 release for the end of August. We understand that this delay is making it difficult, if not impossible, to fully evaluate the product. Installing the 1.4.2 maintenance release will assure that your Trial period does not run out before 1.5 is released. We are especially concerned for our existing customers who are counting on hierarchical support. But, we feel that meeting quality standards takes precedence over meeting deadlines. We will not release something with known bugs and "fix it as we go." When it is ready, 1.5 will be released only to our current customers as a Beta version. A Final version will be released for download by our customers, and as a Trial version to the general public, after we have received sufficient feedback, can be comfortable that it has been tested in a wide variety of environments, and have fixed any hidden issues. We appreciate your patience and believe it will be well rewarded, as the hierarchical API is shaping up very nicely.
- Hierarchical support
- Caching
Future Enhancements
We have not forgotten the other features requested. In fact, we are using a new issue tracking system that helps us keep tabs on over sixty items, from ObjectDataSource support to updateable Views. Rather than try to predict when these will be ready, our focus is on putting out a top-notch hierarchical release. As we get closer to delivering it, we will prioritize what we have and post a roadmap for 1.6 and beyond. The new system has already reduced the amount of administrative time we spend on tracking bugs and enhancements. That means more time is available to actually code on them 
The EntitySpaces Team