Skip to content

Releases: gggeek/ezdbintegrity

0.14.2

20 Jan 23:24
Compare
Choose a tag to compare

Fix 2 FK checks (bug introduced in 0.14)

0.14.1

20 Jan 19:45
Compare
Choose a tag to compare
  • Made code more robust in case there are problems connecting to the db because of bad legacy config (eg. no ini settings files at all)

  • Fixes for changes introduced in version 0.14:

    • fix FK checks that use the same table as both parent and child in joins
    • fix FK checks that have extra WHERE conditions

0.14

01 Jan 17:38
Compare
Choose a tag to compare

. rewritten FK checks to use LEFT JOIN instead of NOT IN (SELECT ...). This should lead to noticeably faster execution, especially on big databases, at least for MySql.

. taught the code to check FK definitions involving 2 or more cols

. rewritten some "custom query" checks as FK checks

. added some FK definitions that use 2 columns

. added a few FK definitions for common extensions as well as some for the core database

0.13.0

02 Dec 23:51
Compare
Choose a tag to compare
  • added one more custom query to check eznode_assignment table

  • fixed one custom query

  • made core more resilient: accept custom queries that end in a semicolon

New command-line options

01 Dec 18:07
Compare
Choose a tag to compare
  • when using the -v command line option, all scripts now output violations as soon as they find them, instead of waiting for the end of the script

  • the checkschema.php script has 3 new command line options that make it easy to avoid checks which take a long time: omitforeignkeys, omitcustomqueries and omitcheck

0.11.0

07 Nov 16:40
Compare
Choose a tag to compare

added 5 new custom queries that verify referential integrity of contents and versions

allow cli scripts to be interrupted with ctrl-c and still display their output

26 Jul 08:31
Compare
Choose a tag to compare

Also: fix 2 queries for checking schema validity (would not run on all mysql versions)

Better output for db schema checks

04 Jul 09:10
Compare
Choose a tag to compare

. give more feedback while checking db schema (useful when checking big databases)

. checkstorage command has gained an option to only validate offending rows for foreign keys, not mismatched column definitions (useful because in the default eZPublish database schema there are still some violations)

NB: output of all commands on the cli has changed

Add support for cluster mode for storage checking

20 May 14:47
Compare
Choose a tag to compare

Add storage checking and attribute validation for ezmedia datatype

20 May 14:48
Compare
Choose a tag to compare