Kenneth, > the whole idea of having an rdbms is that it maintains > integrity of data. And data without unique primary keys is not > data, it is junk
Well, if my app can't manage to respect the data integrity, then my app is junk! I have no objection against data integrity either, redundant but necessary enough. The point I was making was, what's the difference between a primary key vs. any other unique field? > If you are going to waste time and code > maintaining data integrity in your application logic, you might as > well use flat files to store your data. I've done so a few times: (al addin sur faces dot com) The result was rather painful :) > Either use the engine or use something more lightweight to ease the > burden on the horse. hemm. So, database by definition is heavy/inefficient in regard to scalability? If so, please instruct me with some pointers where I can better approach my current project as I am still in planning phase. Thanks, Mike
