[Resolved] local if no connection

[niklas_pang_it]

Hello everybody. I'm all new to this, used to work in asp, but... I know NOTHING about php. Well, that's that for an intruduction. I have a question. I hope someone can help me out.

I need to have 5 users getting and updating info in a db, but if there's no connection to the server, the whole thing should work localy without any interruption... (the user shouldn't even know the difference) ...and when a connection is present the users should all update.

Can this be done and what/where should I look for?

Please help this old sinner :-) /Niklas

[laserlight]

What do you mean by "work localy without any interruption"?

Do you mean that users will connect to another server for the DB, but if that DB is unavailable, it will connect to the server's own DB?

That doesnt make sense, since you might as well implement the whole database without using the external server.

Otherwise, you'll have to batch update either server consistently.
i.e. when the local DB is used, once the remote DB is online, it is updated to match the local DB.
Under normal operation on the remote DB, the local DB must be updated to ensure data integrity in case the remote DB fails.

Conversely, you could mean that users work locally on their own computer.
The problem with that is that how are they going to update their info unless there is a location to store it? And if such a location exists, it serves as a database.

[niklas_pang_it]

Yes I mean that users will connect to a server for the DB, but if that DB is unavailable, it will connect to the local server's DB. That is, every client must have its own server.

And it does make a little sence, the idea is for a chain of shops with a warehouse in common to be updated of what's in store. If client 1 sells product y it should be updated in the DB. Very straight forward, no? but if there's no connection (unfortunately something that happens alot in Italy) the system should still keep track of all movements and update as soon as there's a connection to the DB.

I realize the amount of traffic this would generate and was hoping for an intelligent solution.

[laserlight]

Oh, I see.

The implementation depends on how transactions and deliveries are made.

If each shop delivers from its own stock, and only requests re-supply from the warehouse when needed, then:
Do all transactions locally.
After closing hours (or whatever suitable time), update the central database.

On the other hand, if each shop requests delivery from the warehouse immediately, there is a problem.
On normal operation, the transaction is done locally, but sent to the warehouse DB concurrently.

The service personnel will need to contact the warehouse personnel by say, telephone, and the delivery is made.
If the connection to the warehouse is not available, the service personnel should receive an error message, upon which they will also notify the warehouse to update the central database.

[niklas_pang_it]

That is a good idea. I do thank you. It could well work.

I still have no idea of how to code it, but that's an other story.

If anyone else has other ideas about this, please feel free to share /Niklas