v16.1 Project integrity check SQLite (and MS Access) vs SQL Server

[Paolo F Cantoni]

We've been investigating using SQLlite for our snapshot clone repositories (since MS access is failing due to repository size exceeding 2GB).

We (project) transferred our SQL Server repository to an SQLite .qea repository, and we then checked the .qea repo for consistency.  It found an inconsistently named package (it had a trailing space)!  Oh-oh, we thought Sparx had done it again; over a decade ago, we proved to Sparx that the project export/import was failing (since they could seem to grasp the testing process required to prove it worked).  But then we investigated the underlying data in the database and found that, indeed,  t_package.name had a trailing space and t_object.name did not!

So the defect was NOT with the Project Transfer, but with the Project Integrity Check!  (It's difficult to say which is more critical!).  This package has been in the SQL Server repository for years!   The Project Integrity Check for SQL Server did not pick it up through all the previous versions of EA (we're currently running v16.1 b1624)!  Since we assumed that the Project Integrity Check was sound, we didn't check the MS Acces Clones (since we went into them only very rarely as required).  We now note that the  Project Integrity Check for the MS Access clone also detects the Inconsistently named package.

This needs to be rectified ASAP (as does the coding process that generated the error in the first place!)

Reported,
Paolo

[Sunshine]

Well spotted and I couldn't agree more.