On Tue, Oct 14, 2008 at 9:56 AM, Alex Chamberlain <php@xxxxxxxxxxxxxxxxxxxxx > wrote: > Thanks for your suggestion!! Sounds like a good route to go down with the > API access. Really struggling with the pending 'list' at the moment. Suppose > I have got 2 tables `product` and `description`. `product` contains `EAN`, > `name`, `last_modified` and `description` contains `EAN` and `description`. > The nearest thing to me right now is a tub of pencils. > > EAN: 5011772007888 > Name: 50 Staedtler HB Pencils > Description: A tub of 50 HB Pencils by Staedtler. > > Suppose someone at BarcodeDB.com, having signed in, wanted to change the > description to: A tub of 50 HB Pencils by Staedtler. With strong break > resistant leads, they make an ideal pencil for kids or adults alike. > > Rather than update this description straight into the database. It would be > nice for it to wait to be approved, and once approved a 'history' is kept so > it is known who submitted the data and who approved it. Any ideas on how to > achieve this effectively?? > > Thanks, > > Alex > > No virus found in this outgoing message. Scanned by AVG Free 8.0 > Checked by AVG - http://www.avg.com > Version: 8.0.173 / Virus Database: 270.8.0/1722 - Release Date: 14/10/2008 > 02:02 > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > **I would cue it up in an XML file-based queue, storing all changes in that queue and letting an admin go thru it as they have time. When the review is committed, the xml can be processed and the database updated. If the review is rejected, remove the xml from the queue. -- Bastien Cat, the other other white meat
