Bug#513106: dbconfig-common: provide a script to check sql schemas
Control: tags -1 moreinfo Hi Thomas, I have taken over maintenance of dbconfig-common from Sean. On Mon, 16 Mar 2009 22:26:47 +0100 sean finney sean...@debian.org wrote: On Mon, Jan 26, 2009 at 02:39:57PM +0100, Thomas Koch wrote: Unfortunately at least MySQL does not provide any means to syntax check a sql script. But the script could create a temporary database and try to install the given schema (and data). i'm not sure what it is you want that dbconfig-common doesn't already do. in the initial bootstrap i don't think this gets us any advantage over simply doing it, since it would be doing the same operation twice, dbconfig-common already checks for errors in the process, and we're starting from nothing so there's no risk in failure. for upgrades, this would test that the sql is correct, but not know how it behaved on the real data. what you really want is a transaction so that if there's a failure a rollback can occur. no new feature in dbconfig-common is needed for this, the package maintainer simply needs to add a transaction start/commit to the existing upgrade code. is there some other use case i'm missing, or is it okay to close this bug? Can you please comment? Else I am going to close this bug in a month or so. Paul signature.asc Description: OpenPGP digital signature
Bug#513106: dbconfig-common: provide a script to check sql schemas
hi thomas, apologies for the late response... On Mon, Jan 26, 2009 at 02:39:57PM +0100, Thomas Koch wrote: Unfortunately at least MySQL does not provide any means to syntax check a sql script. But the script could create a temporary database and try to install the given schema (and data). i'm not sure what it is you want that dbconfig-common doesn't already do. in the initial bootstrap i don't think this gets us any advantage over simply doing it, since it would be doing the same operation twice, dbconfig-common already checks for errors in the process, and we're starting from nothing so there's no risk in failure. for upgrades, this would test that the sql is correct, but not know how it behaved on the real data. what you really want is a transaction so that if there's a failure a rollback can occur. no new feature in dbconfig-common is needed for this, the package maintainer simply needs to add a transaction start/commit to the existing upgrade code. is there some other use case i'm missing, or is it okay to close this bug? sean signature.asc Description: Digital signature
Bug#513106: dbconfig-common: provide a script to check sql schemas
Package: dbconfig-common Version: 1.8.39 Severity: wishlist It would be fine to have a command, that would automatically check the sql scripts. Unfortunately at least MySQL does not provide any means to syntax check a sql script. But the script could create a temporary database and try to install the given schema (and data). -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dbconfig-common depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii ucf 3.0011 Update Configuration File: preserv dbconfig-common recommends no packages. Versions of packages dbconfig-common suggests: ii mysql-client 5.0.51a-21 MySQL database client (metapackage ii mysql-client-5.0 [virtual-mys 5.0.51a-21 MySQL database client binaries -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
