As far as "grainy" text is concerned, I mean text made of text and so on... we're back to hierarchical databases, the modern version being XML databases. The big advantage is that you can design a very simple dbase in term of schema. Then you can pour into it complicated structures (sgml, XML..) that you can retreive in whole or partially at will. It does require more processing power of course, but we have it now!
You can find some source in "editorial databases" as this kind of things were really digged at the birth of sgml 20 years ago. It can be very simple. I've got a model working fine as the database of highly structured books in an editorial process application, that deals with extracting any part of a book and outputing in different formats. Feel free to drop an email. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/OT-Resources-for-Data-Base-Design-tp2144237p2171813.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
