developer's mag
main page
article
part 1
part 2
part 3
part 4
part 5
part 6
part 7
part 8
8 - Conclusion
There is little error checking in the code, allowing you to do all manner of silly things, like writing to an unopened database, or not closing. Although production code needs to check for invalid states, this example code allows us to see exactly how the code will blow up under certain conditions, and to consider how to protect against it (especially the issue of data recovery if a database is well and truly corrupted).Note that these wrapper functions are simply a way to handle database calls more generically. Feel free to gut them and place the actual db calls in your own programs. On the other hand, if this is all the functionality you need, these calls may make database working easier. They help compartmentalize the necessary code to access ebm databases, saving rewriting and the potential bugs with each rewrite. Using them, you're ready to start simple database manipulation on the ebm.
Previous Section