Jochen Lillich wrote:
> But now, we have a project whose data model doesn't fit well with the
> article paradigm Midgard is based on. We'll have to manage product
> data, contact addresses etc. Of course, this could be done in plain
> PHP, using .php files, FastTemplates, PHPlib and so on.
>
> But I fell in love with the content/layout separation Midgard enables
> me to do. My thought: What about using Midgard for that purpose and
> administration only and doing all the data management the normal PHP
> way?
>
> Would this be a wise step, giving us comfortable administration but
> keeping data flexibility? Or would it be overkill, making an easy task
> much too complicated?
With the current (1.4) release, if your data doesn't fit into the
topic/article 'format' it's probably a kludge to use it. Using
separate tables/database makes perfect sense. We're working on getting
the data format more flexible in 2.0 but even then there will on
occasion be good reasons to have data outside the Midgard database.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
