On Tue, Oct 14, 2008 at 9:56 AM, Alex Chamberlain <[EMAIL PROTECTED]
> 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` cont
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 `descript
On Tue, Oct 14, 2008 at 9:56 AM, Alex Chamberlain
<[EMAIL PROTECTED]> 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` cont
Alex Chamberlain 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.
Seems to me that 'pending' is just a flag - your list is then all of the
codes with flag=pending.
> Suppose someone at B
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 `descript
Alex Chamberlain wrote:
I wish to set up a similar website. Indexed on the modern EAN-13 (used
across the world, and includes ISBNs), the database will store a barcode and
name for *every* product. Additionally, the description of the product can
be stored. In the future, I would like to implemen
6 matches
Mail list logo
