I develop exactly the way you're approaching it: Local MySQL development,
then when everything's ready, move it to the server.
I just do a dump of the db locally, then use the SQL area of phpMyAdmin to
plop it into the server's MySQL. Bada-bing, you're done.
So long as you're careful to mirror the exact db name, username, and pass on
your local machine as what they are on the remote server, your scripts
should connect to the db just fine. I always set up the db first on the
remote server, because they usually prepend the account's username to the db
name and db username. Then I just create the exact same db and user on my
local machine.
--
Sonjay
On 7/9/07 11:50 AM, "Charles Newbury" wrote:
> I'm using DW8 on OS 10.4.10.
>
> At this point I have a local testing server set up using OS X's built-in
> Apache for one of my sites which also uses some php forms. Works fine, but
> I'm at the point of development where I will need a MySQL database. My
> webhost has MySQL and php so that's good.
>
> I found it fairly easy to start the MySQL DB locally but am completely
> unsure, if I go this route, how to get the locally developed MySQL DB to my
> webhost server. So far, I've been experimenting and find DW easily connects
> to the local DB and has the scripts to list, input and modify data.
>
> On the other hand, I believe I can set up the remote webhost as my testing
> server and develop the DB there. It has phpMyAdmin via browser. If I do,
> there should be no problem syncing the data?
>
> Nevertheless, I feel more comfortable developing locally. That way, if I
> mess up, at least the mistakes won't automatically show up on the internet.
> But my concern also is that scripts pointing to a local virtual server,
> won't automatically translate on upload to the remote webhost DB.
>
> Can anyone clear this issue up for me or point to information that will?
>
> Thanks
>
> Charles Newbury
> >> Stay informed about: Advice? Local/Remote Testing Server - php/MySQL