Re: The Zen nature of a Delphi database application
- From: Hans-Peter Diettrich <DrDiettrich1@xxxxxxx>
- Date: Sun, 18 Feb 2007 19:14:58 +0100
marek jedlinski wrote:
I do have classes that register themselves and factories that create them
based on some form of ID that a single class responds to. But for storage,
it immediately implies a "god class" that first loads a "metatable" with
class IDs of the actual data objects. So there are now at least two tables
which must be kept in sync: the metatable (classID, objectUID) and one or
more tables for the objects themselves.
In addition the class definitions in source code must be kept in sync with the database. I don't think that it's a good idea to have databases, which can become corrupt or otherwise unusable when the source code of the related programs is changed. If you want more flexibility, use XML and store information strictly as text.
DoDi
.
- References:
- The Zen nature of a Delphi database application
- From: marek jedlinski
- Re: The Zen nature of a Delphi database application
- From: Bjørge
- Re: The Zen nature of a Delphi database application
- From: marek jedlinski
- Re: The Zen nature of a Delphi database application
- From: Maarten Wiltink
- Re: The Zen nature of a Delphi database application
- From: marek jedlinski
- The Zen nature of a Delphi database application
- Prev by Date: Re: Editor component
- Next by Date: Found the problem. INCREDIBLE!
- Previous by thread: Re: The Zen nature of a Delphi database application
- Next by thread: Re: The Zen nature of a Delphi database application
- Index(es):
Relevant Pages
|