I wrote a mass of python scripting code to do this for me, parse the
generated app.dbd file then parse the substitution files and databases.
I also do sanity checking for things like invalid field names, invalid
menu selections, duplicate record names, duplicate fields in records,
links pointing to non-existent records, aliases with non-existent
targets... pretty much every stupid mistake I can remember myself making.
On 4/23/2015 5:56 AM, Ralph Lange wrote:
Dear all,
Ages ago I remember there was a tool called 'dbst' that could be used
to validate DBD/DB setups and that could dump DBs in a sorted,
normalized way (only non-default value fields, standard indentation)
to make them easily comparable with diff and such.
Is dbst still around? I suppose there are more recent ways nowadays.
Perl/Python? Web-Service?
(I do like the idea of using the same library as the IOC, though...)
What is a good way to do database validation?
Thanks a lot,
~Ralph
--
John A. Priller | Phone : (517) 908-7375
MSU Cyclotron Laboratory | Email : [email protected]
640 S. Shaw Lane room 4220Z | Web : http://people.nscl.msu.edu/~priller/
East Lansing, MI 48824 |
- Navigate by Date:
- Prev:
RE: DBD/DB validator? Allison, Stephanie
- Next:
RE: DBD/DB validator? Lang, Keenan C.
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: DBD/DB validator? Benjamin Franksen
- Next:
RE: DBD/DB validator? Lang, Keenan C.
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|