Comments for A Few More Words

Comment on Agile Database - Part 4: MIGRATEdb (a solution to the release problem) by warren

warren — Mon, 13 Oct 2008 09:42:30 +0000

I am not a MySQL specialist. I would have a look at a few books in my local bookstore, or type Mysql into Amazon and read about what comes up.

Comment on Agile Database - Part 4: MIGRATEdb (a solution to the release problem) by werutzb

werutzb — Wed, 08 Oct 2008 02:01:32 +0000

Hi!

I want to improve my SQL capabilities. I red that many SQL books and want to read more about SQL for my work as mysql database manager.

What can you recommend?

Thanks, Werutz

Comment on Repository or DAO? by JAOO Brisbane: Goldilocks and the Concurrent Processes at A Few More Words

JAOO Brisbane: Goldilocks and the Concurrent Processes at A Few More Words — Thu, 29 May 2008 10:44:47 +0000

[...] complexity. Getting your design just right is a primarily a craft. It may be helped by things like Domain Driven Design or reducing irreversible architecture choices by removing them or delaying them. Software [...]

Comment on Building a better BeanProcessor by warren

warren — Sat, 03 May 2008 08:45:08 +0000

@Karim: Have a look at resultsetmapper. It is the open source implementation of the discussed problem.

It can map resultset data to java beans (and their 'aggregate' components) in 2 ways:

via annotations in the java bean
via naming conventions and slight configuration (ie a list of the aggregate classes).

Please let me know if it is of use, or if you would like me to improve in some way.

Comment on Building a better BeanProcessor by Karim

Karim — Fri, 02 May 2008 21:02:55 +0000

Ive been working on a framework built on DbUtils, which sole intention is to simplify database work to a single object that can be used simply in many threads. The one feature I really would like to add is the "aggregate" concept you referred to in your bean mapper. Do you have a working version of this, and could I use it in my project (of course you will be given full credit). The project is being released under the apache 2 lic.

Thanks in advance for your consideration,

Karim

Comment on Agile Database by Max Guernsey, III

Max Guernsey, III — Wed, 30 Apr 2008 19:48:39 +0000

You might also try DataConstructor. It is not open source but there is a free trial.

We also offer a series of articles on database agility that starts with a little bit different perspective from the norm.

Comment on Agile Database - Part 2: The release problem research by Max Guernsey, III

Max Guernsey, III — Mon, 10 Mar 2008 23:13:31 +0000

You might also consider a series of articles I am writing:

Rethinking Agility in Databases

It explores how the practices we've developed for Agile software development need to be changed to adapt to the demands of a database.

Comment on Agile Database - Part 2: The release problem research by warren

warren — Wed, 06 Feb 2008 23:24:46 +0000

Some more articles:

Three Rules for Database Work

Versioning Databases â€“ The Baseline

Versioning Databases â€“ Change Scripts

Versioning Databases â€“ Views, Stored Procedures, and the Like

Versioning Databases â€“ Branching and Merging

Comment on Repository or DAO? by Koert

Koert — Wed, 09 May 2007 12:02:19 +0000

I think the comment "including business representatives to whom DAO would need constant explanation" is the most compelling reason to use Repository instead of DAO. Otherwise, I see little difference between them.

You could just use Hibernate directly in the Repository, since it provides an abstraction to the persistence anyway. I think it's theoretically a good idea to layer the persistence in a DAO layer so you can replace it easily, but it requires more work and costs.

I would prefer to use Location as parameter to find: find(Location location).

Comment on Agile Database by Milan

Milan — Mon, 22 Jan 2007 01:53:09 +0000

Another opensource solution worth mentitioning is http://dbdeploy.com/