[isf-wifidog] WiFiDog Roadmap, first draft
wirelessguy at optonline.net
Mer 8 Juin 18:28:20 EDT 2005
Just a thought here, but would it be possible to split out development
changes from PHP and Postgres?
Perhaps there is a way to use revision numbers like
This way you can update the php many times and let users know when a
specific php change will also bump up the db version number you need.
I suppose that someone will think of a more elegant solution, but I thought
I'd throw it out for folks to chew on a bit.
At 06:02 PM 06/08/2005, you wrote:
> > On the other side, for others developpers (and me) postgresql is a pain to
> > use in comparaison with mysql. I can't understand why we must develop the
> > auth-server schema in postgresql (or any DB) and not in a DB design GUI
> > like DBDesigner (abstraction).
>We... don't. The problem is that when someone updates the database schema
>because of some code change, there has to be a way to communicate the ewxact
>changes made to the schema so people can upgrade their database. The only
>way to do that is to send a bunch of alter tables. Since saying "put them in
>the changelog and people will read it there" just didn't cut it,
>schema_validate was developed. Now everyone who already uses wifidog are in
>sync and happy.
>The problem is new users, we have to publish a complete initial schema
>up to date, as well as initial data. The only way to do it with no mistakes
>is to generate it directly from a running database.
>Untill there are free db design tool that can do diffs between two schemas,
>that's the only way to go.
> > I don't know what DBdesign worth (any power
> > user of this tool somewhere ?) but maybe it can solve some developpment
> > issue.
>I used to use it, it's a great tool. Unfortunately at the time it's foreign
>key handling was buggy, and it was only happy with MySql.
>Benoit Grégoire, http://benoitg.coeus.ca/
>WiFiDog mailing list
>WiFiDog at listes.ilesansfil.org
More information about the WiFiDog