Even though my first experience with a DB was with DB2 at the university what I ended up using at home, at first, was MS SqlServer 2000. As my project needed some sort of hierarchical category system I wanted to create a table that is self referencing itself and can do ON DELETE and ON UPDATE CASCADE triggers. Unfortunately MSSQL2K did not support this feature (I don't understand how you can do any reasonable graph data structure without it) so I had to make some scamontage tricks (google for CELKO tables and nested set) that I didn't like. I eventually tried the same thing with DB2 and it seems to work but it's out of the question as it's not free. It seems that mySql for the moment has a limit on the recursion depth of the triggers. What surprised me is that it seems PostgreSql supports such tables so at the moment it looks it'll become my favorite DB.
Posts
Showing posts from July, 2005
- Get link
- X
- Other Apps
These several weeks have been rather fast paced. Even though I can't dedicate enough time on my project I've developed some thoughts on it. I still like my filter based controller, what I think I did wrong is that at the current moment I use my DAO's directly in the Actions. This is fundamentally wrong even though it gets the work done and is ok for this first phase of development. I intend to wrap these things in the Managers and stop using DAO's and DAO factories directly in that layer. Next change I plan to implement is a validation framework. I would like to use the annotations in the Java5 platform to acomplish this. Spring and OR via Hibernate comes right after :)