Thread: Web application development on Win32, deployment on Linux
I currently maintain a website which is deployed on LAMP, but it is developed on Windows (WAMP?). I'm considering moving both to use PostgreSQL. I'm curious as to whether others are following a similar development/deployment model and if so, what pitfalls/gotchas they have found. For example, I refresh production tables on a weekly basis from the development database. Linux MySQL is case-sensitive about table names but Windows isn't, so I have to modify table names like 'whatsnew' on Windows to 'WhatsNew' before I can run the reload script on Linux. I'm also interested in any replication experience in such a scenario since the current export/modify/import process is done manually, in particular the determination of which tables changed from week to week. Another concern about the move to Postgres is that the website's current Search capability is based on MySQL's full-text search functionality [SELECT ... WHERE MATCH (...) AGAINST (... IN BOOLEAN MODE)] . PostgreSQL doesn't appear to have something resembling that. I'm curious as to third-party solutions or development plans. Joe
> I currently maintain a website which is deployed on LAMP, but > it is developed on Windows (WAMP?). I'm considering moving > both to use PostgreSQL. I'm curious as to whether others are > following a similar development/deployment model and if so, > what pitfalls/gotchas they have found. For example, I > refresh production tables on a weekly basis from the > development database. Linux MySQL is case-sensitive about > table names but Windows isn't, so I have to modify table > names like 'whatsnew' on Windows to 'WhatsNew' before I can > run the reload script on Linux. There should be no such differences on PostgreSQL. The one major pitfall there is that UNICODE encoding is not fully supported on Win32. Yuo can use ut, but things like sorting and upper/lower does not work. [snip replication - can't answer that] > Another concern about the move to Postgres is that the > website's current Search capability is based on MySQL's > full-text search functionality [SELECT ... WHERE MATCH (...) > AGAINST (... IN BOOLEAN MODE)] . PostgreSQL doesn't appear > to have something resembling that. I'm curious as to > third-party solutions or development plans. Take a look at tsearch2, it's in /contrib/. It can fulfill most full-text search needs - it certainly solved all mine. You'll have a different syntax, of course, but you can get the system working. //Magnus
On Mon, Jun 27, 2005 at 01:59:42PM +0200, Magnus Hagander wrote: > > I currently maintain a website which is deployed on LAMP, but > > it is developed on Windows (WAMP?). I'm considering moving > > both to use PostgreSQL. I'm curious as to whether others are > > following a similar development/deployment model and if so, > > what pitfalls/gotchas they have found. For example, I > > refresh production tables on a weekly basis from the > > development database. Linux MySQL is case-sensitive about > > table names but Windows isn't, so I have to modify table > > names like 'whatsnew' on Windows to 'WhatsNew' before I can > > run the reload script on Linux. > > [snip replication - can't answer that] Regarding replication, the Slony-I guys state that their project is not yet ported to Windows, but giving that there is a pthread library for Windows (which is about the only thing it lacks, apparently) then it should be possible to port it rather easily. I'm sure they'd welcome it if somebody were to do the legwork. I know of several people who would be very glad to have Win32 Slony-I. -- Alvaro Herrera (<alvherre[a]surnet.cl>) "La Primavera ha venido. Nadie sabe como ha sido" (A. Machado)
> > > I currently maintain a website which is deployed on LAMP, > but it is > > > developed on Windows (WAMP?). I'm considering moving both to use > > > PostgreSQL. I'm curious as to whether others are following a > > > similar development/deployment model and if so, what > > > pitfalls/gotchas they have found. For example, I refresh > production > > > tables on a weekly basis from the development database. > Linux MySQL > > > is case-sensitive about table names but Windows isn't, so > I have to > > > modify table names like 'whatsnew' on Windows to > 'WhatsNew' before I > > > can run the reload script on Linux. > > > > [snip replication - can't answer that] > > Regarding replication, the Slony-I guys state that their > project is not yet ported to Windows, but giving that there > is a pthread library for Windows (which is about the only > thing it lacks, apparently) then it should be possible to > port it rather easily. I'm sure they'd welcome it if > somebody were to do the legwork. I know of several people > who would be very glad to have Win32 Slony-I. Dave, Andreas, me and Hiroshi are working on this. It's not at top-speed right now due to the main projects feature freeze, but work is in progress, and it's definitly doable. (Hey, I knew that. Should've answered from the beginning :P) //Magnus
On Mon, 2005-06-27 at 10:50, Alvaro Herrera wrote: > > Regarding replication, the Slony-I guys state that their project is not > yet ported to Windows, but giving that there is a pthread library for > Windows (which is about the only thing it lacks, apparently) then it > should be possible to port it rather easily. I'm sure they'd welcome it > if somebody were to do the legwork. I know of several people who would > be very glad to have Win32 Slony-I. Actually, the port is well underway, and JUST missed the cutoff for 1.1. Might well show up for 1.1.1 or so.