> Description ----------------------------------------- > > The client wants to put and then weekly update her price-list on the > site. The list, in its hard-copy version, is a table with the > following columns: car's model name, its manufacture date, and price. > > On the web, it's planned that a price-list position may have a photo > attached to it. Also, it should be possible for a visitor to filter > the list on the price or model name column. > > Well, on the other hand, our client needs some kind of an > administration interface being setup to let her update the price-list. > > 1. What would be the best way to store price-list items of the > forementioned structure inside the Midgard DB?
If I were you, I would not store it in the Midgard DB. Midgard db is a _content_management_ platform, so OK for managing unstructured data such as the text that has to appear on a website. If you want to manage structured data (especially numeric data such as prices), create you own database/tables and manage it with custom made scripts (I would even put that functionality into plain php files you include in your midgard pages or styles - this way you can use nice abstraction layers, such as http://pear.php.net/manual/en/packages.database.db-dataobject.php). > > I could actually put the data into a separate database table, but > then, AFAIK, it wouldn't be possible to replicate the site as a single > chunk using repligard. True, but it doesn't seem worth the effort of stretching Midgard to match your requirements. pascal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
