in reply to Re^2: Testing database updates.
in thread Testing database updates.
I dare say that I will soon have to pass the XML output
XML? Did you choose that format? Looking at the help from my copy of sqllite3 XML isn't even an option:
.mode MODE ?TABLE? Set output mode where MODE is one of: csv Comma-separated values column Left-aligned columns. (See .width) html HTML <table> code insert SQL insert statements for TABLE line One value per line list Values delimited by .separator strin +g tabs Tab-separated values tcl TCL list elements
Unless you chose HTML? Or did they add an XML option recently?
Choosing XML over the ,dump SQL format (IMO) is a big mistake. The SQL format is so simple to manipulate and compare:
sqlite> .dump onegb PRAGMA foreign_keys=OFF; BEGIN TRANSACTION; CREATE TABLE onegb ( alpha varchar, no varchar, hex varchar, bin varch +ar ); INSERT INTO "onegb" VALUES('nvbqurkn','05812224','42295f70','"Mƒp®Iÿ&# +9618;SpæÕ¦├ƒ±¦c²NB͹sÙ-¼┐ºâ5ó<Ú="'); INSERT INTO "onegb" VALUES('xzpviekv','72456229','fd245120','"ª¿.ν +1;¡ù©=àô²Ð╣j‗Èl╝°¾©▓º§~zo=¬fIí┬Z"'); INSERT INTO "onegb" VALUES('qrkhwqwl','43135665','316f7a36','"æe╗ +;´Í└╬┴╚╔¸Éwf±Û6lòêqc¸▄iZñƒ┤ +}E⌂¤┤"'); ...
(Okay. That's not the most complex schema in the world; but one advantage of sqlite for this kind of thing is that it actually uses very few different datatypes.)
Whereas comparing XML is a nightmare. Less so I suppose if you don't have to worry about the attributes/nested sub-items equivalence -- I assume that however you are generating the XML, it at least produce consistent XML.
I think you are making hard work for yourself using XML, but as I said above somewhere, it is your choice. Good luck :)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Testing database updates.
by chrestomanci (Priest) on Apr 20, 2012 at 08:09 UTC |