Re: Confusion about database updates
From: David Harper (devnull_at_obliquity.u-net.com)
Date: 04/12/04
- Previous message: Burhan Khalid: "Re: Confusion about database updates"
- In reply to: Burhan Khalid: "Re: Confusion about database updates"
- Next in thread: Glacial Spain: "Re: Confusion about database updates"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 12 Apr 2004 18:47:29 +0100
Burhan Khalid wrote:
> The problem here is that the primary key, which is auto incremented,
> is part of the printed record for each transcation.
>
> Consider an invoicing application. The primary key would be the
> invoice number. So when a customer requests a printed invoice, we
> have to generate an invoice number.
Here's a possible solution, which doesn't depend upon your sales people
being able to connect to the master database at your head office at all
whilst they are travelling and making sales.
I'm guessing that your sales people have laptops. You can run a MySQL
server on a laptop running Windows. Design your application so that it
stores invoice information to the MySQL server on the laptop. That way,
all of the transactions stay in the laptop.
Also, give each of your sales people a unique username, and require them
to "login" whenever they start up the client application. Their username
is logged to the laptop's database as part of the invoice information.
When your sales people visit your head office, they run a second
application which transfers all of the new invoices from the MySQL
database on their laptop to the master MySQL database.
> Thank you for your suggestions though, I appreciate your time
You're very welcome. We're here to help :-)
David Harper
Cambridge, England
- Previous message: Burhan Khalid: "Re: Confusion about database updates"
- In reply to: Burhan Khalid: "Re: Confusion about database updates"
- Next in thread: Glacial Spain: "Re: Confusion about database updates"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|