Thanks Andre - I've used that sort of approach in the past but the guys providing the content on this project are very protective of their stuff (images) and a 'real' database seems the best option.
Regards, Terry... > Terry, > why not keeping the images as external files and putting a field in the > database with the file path? this would lead to databases with less chunk in > it since to use the images you'd have to output them to files anyway. > > something like this: > > Hard Drive Image ID Table > My Database > myImage.jpg <---------> Record that match id to file <------------------> > field image_id > > This is a simple solution where you use a intermediary table to match id's > with files, this way if you change a file name or path, you just need to > update one table entry and not all your database entries that deal with that > file. This makes easy to "reconnect" lost media files if things move around > in the Hard Drive. > > I would not put media files inside SQL Databases. > > Best > Andre > -- Dr Terry Judd Lecturer in Educational Technology (Design) Biomedical Multimedia Unit Faculty of Medicine, Dentistry & Health Sciences The University of Melbourne Parkville VIC 3052 AUSTRALIA 61-3 8344 0187 _______________________________________________ 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
