I’m building a new web site for DbFit and rewriting the documentation from scratch. For the new site, I would love to have some success stories and comments from people who are using the tool now. So if you are one of them, and you are happy with the tool, pretty please take a moment to write a short comment on what you are doing and how DbFit has helped you – one-liners are welcome as well. Please also ask your manager if I can mention your company name – I would like have a “who is using DbFit” page on the new web site as well. Click here for my contact information or just put the comment into the box below this post.
Thanks in advance.
New version of DbFit (0.92) is now available for download from SourceForge. Here are the most important changes:
Better error handling, DbFit now prints out missing column/parameter names and warns if table/procedure could not be found
- new Inspect fixture to help with regression tests: DatabaseTest has three methods to automate it: InspectQuery, InspectProcedure and InspectTable. These methods will quickly print out entire query results, structure of a procedure or a table/view in a form that can be easily converted to a regression test, or used as a template for ExecuteProcedure, Insert or Update tables.
- support for Oracle procedure and package synonyms
- Type details are read from SqlServer in a more efficient way, supporting objects with dots in names and fixing
a few edge cases where duplicate records were retrieved with 0.91
- null keyword handled correctly in Java
For more information, see DbFit project pages
For the last couple of years, I’ve been working with mid-size and large UK bookmakers, trying to introduce agile development practices into those environments on several projects. Although for most of the readers of this blog using agile practices is no longer a question, agile development is fairly rare when it comes to databases, and all these systems were heavily database-centric. About a year ago, I finally found the right formula to do agile development on top of big legacy databases. I presented my experiences at XpDay 07 in London, on a session called “Fighting the monster – agile development on top of legacy databases”. This is the content from that presentation. Continue reading
The DbFit User guide is finally updated to reflect all the changes in the past few months. It is now called Getting Fit With Databases (to reflect that SQLServer and MySQL are also supported), and explains the differences between Java and .Net implementations. Download it from SourceForge.
DbFit 0.91 is available for download from SourceForge.
Most important changes in this release are:
- support for type normalisers in Java, which can transform content coming out of the database. That provides workarounds for JDBC driver inconsistencies and finally brings proper support for Oracle Timestamp, CLOB and REF cursor support in Java.
- New fixture table: Update. This type of table can be used to quickly script data updates. See acceptance tests for examples.
- support for BINARY and VARBINARY types for SQL Server 2005. These map to byte arrays. A utility formatter is also in the release, that allows you to specify byte arrays in hex format (0xABCD…). See the data types page in SQLServer acceptance tests for more information.
dbfit-complete-20071022.zip package contains all binaries (.NET and Java), examples and acceptance tests. Download that package if you want to start using DbFit. For those of you that already have an older binary release in use, I prepared smaller packages with DotNet and Java binaries.