URLyBird: Database schema

[Matt Sheehan]

Is it necessary to read the schema upon execution of the DB? Some of this info already needs to be hard-coded into the client GUI, doesn't it? So is this info ok to be hardcoded for all purposes?

[mike acre]

Nothing needs to be hardcoded anywhere.
Obviously there is sliding scale of complexity depending on how much you hard code.

I would think about rather which tiers can easily be ignorant of there use and which ones make sense to be less flexible and have 'spec nuggets' included, even then you can probably get the hard coded stuff into just two or three classes at most.

I think you will make it easy on your self if your view is specific to the application.

[Matt Sheehan]

Thanks, Mike. That makes sense.

[james airey]

I am taking the approach of hard coding the schema (in a Schema class), but I am also reading it from the DB when I load it, and validating that the 2 are the same.