Developer Diary: Source Control upgrade to Edit 2008.06

LINKS

Site Feed

Developer Diary

Posts, comments, and articles straight from ApexSQL Developers and Analysts

Source Control upgrade to Edit 2008.06

What came to our attention is that I haven't noted anywhere if and how will the new ApexSQL Edit 2008.06 Source Control integration be compatible with the currently available Source Control in Edit 2008.05.

The new Source Control integration will be compatible with most of the existing Source Control mappings. We are planning a detailed and step-by-step knowledgebase articles to explain how to migrate to the new ApexSQL Edit 2008.06 Source Control if you are already using Source Control in Edit 2008.05.

Currently in ApexSQL Edit 2008.05 Source Control a database object can be mapped to virtually any Source Control file. This was identified as application flexibility which was never required and which only caused more problems than good. This is why in Edit 2008.06 we simplified this by introducing implicit object-to-Source Control mapping patterns.

What are implicit mapping patterns? It is just a way to let Edit know how to automatically map database objects to Source Control files. By default Edit will assume that all database Tables exist in Source Control repository in selected Source Control project's "Tables" subproject (subfolder) and that each file will be named as [schema].[name].sql. Similar default mappings are assumed for Views, Procedures, Functions and Triggers. Such defaults will most probably cover 80% of existing Source Control users' needs and 100% of all new Source Control users, making initial Source Control setup much easier and straight-forward.

What if in Edit 2008.05 you already mapped, i.e. all procedures and functions to the same Source Control project and changed extensions to .prc and .fn? Implicit mapping patterns are still configurable and they will cover remaining 15-20% of the current Edit Source Control users' needs. It is possible to individually configure implicit mapping patterns per object type as can be seen on the New Source Control Wizard diary post.

Thanks,
Goran Bogdanovic
ApexSQL Edit Development Team Leader

Get your developers the tools they need to do the job fast and right - ApexSQL Developer Studio is the ultimate combat multiplier for SQL Developers. Best of Class tools - one download, install and discounted price. Click Here for more info.

Labels: ApexSQL Edit

posted by Goran Bogdanovic on Monday, June 29, 2009

0 Comments: