----- Original Message -----
> From: "Dave Page" <dpage@vale-housing.co.uk>
> To: "Andrew Dunstan" <[EMAIL PROTECTED]>; "William ZHANG" <[EMAIL PROTECTED]>
> Cc: <pgsql-hackers@postgresql.org>
> Sent: Thursday, September 01, 2005 3:21 PM
> Subject: RE: [HACKERS] Call for 7.5 feature completion
> > And even those are a royal pain to maintain, never mind an entire set.
> Besides, I'm sure what William really wants is not nmake files, but VC++
> Project files - but then which version do we keep? It's not like we
> could say that everyone should be using VS2005, so all commits would
> have to be VC++ 6.0 or earlier compatible, otherwise someone is bound to
> complain.
You are right. What I want is VC++ projects(*.dsp, *.dsw). Once the
project files is created, the maintance work is simply add/remove some
new/deleted source files (*.c only) from the dsps.
And I think VC++ 6.0 is ok, it is power enough and not so big for pgsql's
development. And latter versions of VC++ can automatically convert 6.0's
project files. There are also a "VC++7 to VC++6 project converter" on
www.codeproject.com.
> I agree with Andrew though - maintaining VC++ project files or nmake
> files is just not practical - especially given that most of our
> developers are not Windows users.
I am expecting more and more Windows users to join us.
According to Andrew's advice, I will try to start a project on pgfoundry
to provide the VC++ project files.
> Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
