pg-nuke-devel Mailing List for PG-Nuke (Page 2)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

--------------------
Looking for a better .sig. Suggestions are being accepted.

---------- Forwarded message ----------
Date: Sun, 11 May 2003 07:34:50 +0200
From: rv...@dd...
To: ma...@al...
Subject: Re: About PHP-Nuke for PostgreSQL

What I will do is do some code cleanup and and send you a diff.
so you can see what it looks like..

Ries

 rvt:

 Sorry if you have already received a reply of your email, but I'm having
some problems with my internet connection.

 Se comments above...

--------------------
Looking for a better .sig. Suggestions are being accepted.

On Tue, 6 May 2003 rv...@dd... wrote:

!Hai Mazza,
!
!thank you for your response.
!
!I didn't do any work on a postgresql port anymore (it's a home project now...)
!because I didn't got any responces from any of the nuke developers.. :(
!I'll do a checkout asap and check it..

 IMO there's no serious developer team, I think that the only one who can
actually code is FB. That's because of the way he treats volunteers. I
still can't believe that he wants to charge $10 to recevei help from
volunteers :oP

!
!Appart from the null insert I also found some other 'strange' effects on the
!SQL part.... I'll check when I'm at home..
!

 Try to list these kind of problems it'll be very helpful. I have been
contacted by a tested intereste in testing PG-Nuke, I hope he'll be very
helpfull to.

!
!What about a next version??? Do you have to do it all over again???
!

 Well, at the beggining I do not pretend to become a PHP-Nuke fork, but
nothing more then a branch, if it becomes necessary in the future we might
become a fork, but only maturity will show us the way.

!What I tryed to do create a SQL rewriter that sits somehwere in the DB layer..

 I though in a solution like this before, but it would probably takes too
much time and would make impossible to keep a branch, I mean, it would
take too long to convert everything again. I have an better idea.

!
!To initialize the database I use a tool to convert a MSQL export to a
!postgresql export which seems to do the job really well (only one change
!in the final output).

 I have used one to my2pg, it's a very inteligent Perl script, very few
adjusts were needed.

!
!What do you do with all the modules create by 3d party developers??

 That's where my idea fits better. I'm planing to develop a small set of
scripts, probably using Perl and/or sed, to automaticly convert special
queries, exactly those which aren't compatible.

 So the first script would convert the NULL insertion that we are having
problem, the other would convert the limit problem, and so on. I think
that it would be the better thing to do, we could generate very fast
converted versions, including 3rd part ones.

 What do you think?

 mazza.

!
!I'll keep in contact...
!Ries van Twisk
!
!Citeren ma...@al...:
!
!>
!>  rvt:
!>
!>  I already have a nuke.sql version for PostgreSQL. If you are interested you
!> can find it at the CVS repository at sourceforge.net/projects/pg-nuke,
inside
!> pg-nuke tree.
!>
!>  As you can see I am really porting PHP-Nuke to PostgreSQL, FB hasn't
aswered
!> my emails so I porting by myself. I'd like to invite you to participate as a
!> developer.
!>
!>  I have already changed nuke.sql and located all INSERT NULL problems.
!>
!>  Hope you get interested.
!>
!>  mazza
!>
!>
!
!

2003	Jan	Feb	Mar	Apr	May (26)	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2004	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

pg-nuke-devel Mailing List for PG-Nuke (Page 2)

pg-nuke-devel — Just for developers