Re: Updating DB Locally

From: Paige (noemail_at_hotmail.com)
Date: 06/21/04 

Date: Mon, 21 Jun 2004 12:55:13 GMT

Michael Austin wrote:
> Paige wrote:
>
>> Michael Austin wrote:
>>
>>> Paige wrote:
>>>
>>>> I have a database on my local machine that I make entries and
>>>> corrections on. I'd like to be able to upload that to my server and
>>>> have that update the database that's on the server. What I've been
>>>> doing is saving the local file as a backup. Then I have to edit the
>>>> backup, deleting the create file info and all previously uploaded
>>>> entries before I can import the text file to the server.
>>>>
>>>> Is there an easier way to do this so I won't get duplicate entry
>>>> notices. I'd like the info from my local file to overwrite the
>>>> server file like FTPing a new web page will overwrite the old one.
>>>> Is this possible to do with mySQL?
>>>>
>>>
>>> First, you have not given enough information to give you the proper
>>> response.
>>>
>>> What platform (specifically the OS)
>>
>>
>>
>> Win XP
>>
>>> Are the corrections/changes DDL (table/column definitions) or DML
>>> (insert/update/delete)?
>>
>>
>>
>> I guess they'd be DML. Nothing changes as to columns or definitions.
>> The only thing that might change would be the info already stored in
>> an entrylike if someone was to move and change their address, that
>> sort of thing. And of course, the new version that I would want to
>> upload would have more total entries than the old one.
>>
>>> Is the data in the database static (read w/occasional updates) or is
>>> it a read/write database (new information stored daily).
>>
>>
>>
>> static
>>
>>> I take it that your "local machine" is a test system and the other is
>>> "production"
>>
>>
>>
>> I guess that's a fair assessment. I want to do the work on my WinXP,
>> then upload the table to the server to replace what is there so I
>> don't have to be online when I want to work on the database.
>>
>>> If you do not care what is in your production database and it gets
>>> over-written with the new version:
>>
>>
>>
>>> Backup/Restore your database from one place to another...
>>>
>>> http://www.phpbb.com/phpBB/viewtopic.php?t=9963
>>
>>
>>
>> Thank you for this suggestion and maybe it's me but this thread seems
>> to involve backing up and restoring phpbb databases on a *new*
>> server/host. If that was my situation, I would have no problem as
>> there would be no entries on the new server so there couldn't be any
>> duplicate ones in the upload. But it's the same table on the same
>> server that I'm looking to do with the new one overwriting the old one.
>>
>
>
> If users of the "production" database can change their information and
> you make different changes to your "local" database, then you must
> guarantee that one does not overwrite the other. Basically you need to
> be able to synchronize your databases not overwrite them... true? Next
> question is this just one table or multiple tables?
>

I am the only one that changes the database entries. There is no form
info being directly submitted to the db and no one else touches it. So
at all times, the db on my computer is the most up-to-date one.

I'm sorry but I don't know the difference between overwriting and
synchronizing a database. I only know that I'd like to be able to upload
the latest db info from my computer to the server and have that one
overwrite, replace, update (or whatever terminology fits) the one that's
on the server.

As it stands right now, the only way I can accomplish this is to either
drop the entire server database and reinstall it using the updated copy
or else I have to edit all the entries in the .sql backup I make to
delete existing entries and mark the ones I changed as UPDATE instead of
INSERT. Neither way is particularly appealing, thus my inquiry as to an
easieer way to do this.

Relevant Pages

  • Re: Updating DB Locally
    ... >>I am the only one that changes the database entries. ... > etc.) but in practice it may be a disaster (lost updates). ... there is no writing done to the database on the server at ...
    (comp.lang.php)
  • Re: Updating DB Locally
    ... >> have that update the database that's on the server. ... >> entries before I can import the text file to the server. ... the new version that I would want to upload would ...
    (comp.lang.php)
  • Re: Saving A database to the desktop
    ... Certinly you could have multiple users using the application independently on their local machines. ... The problem arises when any data changes made by one user will overwrite the existing data on the server... ... User A enters or edits some data, and then re-submits his copy of the database to the server. ...
    (microsoft.public.access.macros)
  • Re: Updating DB Locally
    ... >I am the only one that changes the database entries. ... Since your updates seem to be entered in one place only, ... made on the test server appear almost instantly on the production ...
    (comp.lang.php)
  • Re: Updating DB Locally
    ... the new version that I would want to upload would ... > have to be online when I want to work on the database. ... > entries on the new server so there couldn't be any duplicate ones in the ... be able to synchronize your databases not overwrite them... ...
    (comp.lang.php)