OK, it's the matter of database structure rather

Contents of the http://wiki.tcl.tk/1598 ("A simple database") made me aware,
that the whole problem was rather habit-related.

I mean: when designing the database structure in C or Pascal, there is
usually some kind of table created as a quite obvious first step (rows are
records, columns are records' fields). In Tcl such database can be compared
to a lot of "yellow sticky notes" - each one containing a whole record - and
there's nothing especially wrong, that it all is messed up, just because it
can be instantly ordered (or just "on the fly"), whatever way.
--
ZB
.

Relevant Pages

  • Re: Relational database & OO
    ... The RDB Data Model and the solution's Class Model will typically be different for non-CRUD/USER applications because they need to be optimized differently. ... all the business systems I've participated coding or designing spent little production time changing data. ... Given statistics like these it makes little sense to design your application or OO model before designing your database. ... And OO Class Models are routinely normalized as part of the basic paradigm methodology. ...
    (comp.object)
  • Re: Writing a DAL with TDD
    ... will use the database - which is what you advocated elsewhere. ... designing some new algorithm for a particular business scenario. ... you'll say that we "just" mock those things... ... talented developers, coupled with the strongest ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Writing a DAL with TDD
    ... will use the database - which is what you advocated elsewhere. ... designing some new algorithm for a particular business scenario. ... you'll say that we "just" mock those things... ... talented developers, coupled with the strongest ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: relationship vss join
    ... A AAZ ... B BCJ ... into the database initially, nor one on which referential integrity could be ... In the process of designing a database, ...
    (microsoft.public.access.queries)
  • Re: Writing a DAL with TDD
    ... naive to drive a database design from the point of view of the code that will use the database - which is what you advocated elsewhere. ... The benefits of TDD seem readily apparent - to me anyway - when applied to things like developing an application framework or parsing engine, or designing some new algorithm for a particular business scenario. ... or ASP.NET Web application, where a lot of code MUST interact with external systems or be dependent on things like ASP.NET Application state, Session state, or the HTTP request pipeline, then we're forced to make our unit tests depend on external things like the HTTP request pipeline or an external database. ... Let me see you mock the HTTP Request pipeline and unit test some code that overrides ASP.NET's Application.Init method. ...
    (microsoft.public.dotnet.languages.csharp)