Raymond O'Donnell wrote:
Apologies, my reply should have gone to the list.
To answer your question, the sort of thing I'm thinking of is the
case where, maybe, one copy of a book is missing a page or two (not
unknown in a school library) - the first scenario can't record this,
nor can it tell wh
Shane Ambler <[EMAIL PROTECTED]> writes:
> I have only had a little exposure to barcode scanners - the one that a client
> used just behaved as a keyboard, so there was no programming to support it,
Besides this model there are also models that plug into the serial port and
also USB ports. For b
X-No-Archive: true Excellent.. thank you for that! D.Shane Ambler <[EMAIL PROTECTED]> a écrit : Desmond Coughlan wrote:> X-No-Archive: true> > Just had a thought. If you see .. > > http://www.chez.com/desmondcoughlan/unix/cdi_gt.sqlWith the ISBN number you may want to look at contrib/isn - th
Desmond Coughlan wrote:
X-No-Archive: true
Just had a thought. If you see ..
http://www.chez.com/desmondcoughlan/unix/cdi_gt.sql
With the ISBN number you may want to look at contrib/isn - this adds
ISBN types.
If not then varchar(12) won't hold the new ISBN-13 format that is in
Desmond Coughlan wrote:
And our ultimate aim is for a barcode reader to be used by the librarian.
> Any good sources to learn about that ?
I have only had a little exposure to barcode scanners - the one that a
client used just behaved as a keyboard, so there was no programming to
support it
X-No-Archive: true A really weird thing. This .. http://www.chez.com/desmondcoughlan/unix/bibliotheque.sql .. works almost perfectly. Except for this error .. 'psql:/usr/local/pgsql/bibliotheque.sql:54: ERROR: relation "titles" does not exist' I wrote http://www.chez.c
X-No-Archive: true More tables and fewer columns in the tables? I *like* it! It hadn't occurred to me do it that way. Will this work ? http://www.chez.com/desmondcoughlan/unix/bibliotheque.sql I haven't tested it yet, which brings me to two questions... a. will it work even
X-No-Archive: true Just had a thought. If you see .. http://www.chez.com/desmondcoughlan/unix/cdi_gt.sql .. I'd planned to have one table 'stock' and a column in that table for 'format', as we have books, CDs, DVDs, etc... What about if I had a separate table for books, another f
X-No-Archive: true OK, I think I understand. So the *.sql file that I provided doesn't need to be changed per se, as in the 'stock' table is OK (maybe change it 'stock_general')? I'd just add another table, with a foreign key 'pointing' back to 'stocks_general'... and a sequence, of course, s
Apologies, my reply should have gone to the list.
To answer your question, the sort of thing I'm thinking of is the
case where, maybe, one copy of a book is missing a page or two (not
unknown in a school library) - the first scenario can't record this,
nor can it tell which unlucky borrower ended
X-No-Archive: true Thanks. The main uses will be .. 1. available on www to query catalogue (open to everyone) 2 avail. from the web for teachers and students to check their library account (necessitates an account) 3. available in the library itself both on a web interface (to allow the
X-No-Archive: true Good advice... and no, the 'four tables' was a typo; :) So far, there are only three... I reckon we're not going to split stock into two tables, but your point raises an important question. If I look over my shoulder, say we take Spanish books. There are six or seven co
12 matches
Mail list logo
