Beta 0.10

A quick fix for a potential issue the boys at Agility discovered.

The default SQL metadata query can sometimes not pick up a primary key if  it has other constraints against the column. If you are familiar with the default query it just gets a top 1 on the constraints linked to the column, so if there are multiple constraints you aren’t necessarily going to pick up the “PRIMARY KEY” constraint all the time.

For now I’ve limited the constraints to being “IN (‘PRIMARY KEY’, ‘FOREIGN KEY’)”. The compatibility checker will modify the particular query for you when you load an older version.

The issue with multiple constraints has got me thinking, what about if you want to get just indexes? <<!for idxcolumn col in tablevar!>>

Another little nugget to implement in there.

Anyway, there were a couple of other little issues:

• The “adduseonly” and “addignore” functions weren’t behaving correctly.
• It would have been nice to indicate “project/folder/paths” for packages within any project folders. So this was put in there. Nice.

What’s for Beta 0.11? Well hopefully:

1. CodeDOM implementation. Call .NET code from within a template.
2. Execute a SQL script against a source.
3. It would be really frikken handy to enable repositioning of tabs (grab and slide).
4. Variables and probably templates declared against a symbol table.
5. Another nice feature <<!for table tbl in table!>>. Meaning loop through tables linked to a parent table by foreign key.
6. More code completion tweaks and enhancements.

After this we should be good to go for version 1.0. Promise!

Beta 0.9

Changes for this release:

• Transformations added.
• Console debugging window added.
• Parsing optimisations.
• Pre-compilation has been disabled since the optimisations are fast enough to not need it.
• Some more eye-candy and general “polishing”.
• Many bug fixes, and the code completion has been improved and is less annoying.

Transformations are applied for each row of meta-data, and defaults are added to the SQL Server, Oracle, and Access source providers.

A symbol table implementation has not been performed as of yet. It is quite an invasive piece of work to do, so it will have to wait until another iteration. Also, I was hoping to enable codeDOM execution and direct script execution against a database connection, but again this will best best applied in a future iteration. The current changes need time to settle.

Documentation will be up soon, it is the next priority.