Hi,
I'm currently working on improving Npgsql's
NpgsqlCommandBuilder.DeriveParameters method which is intended to
automatically populate parameter information for a NpgsqlCommand.
As Shay Rojansky suggested to use a Parse/Describe ->
ParameterDescription/RowDescription over the backend
Andres Freund wrote:
That seems like a pretty straight forward bug. But it hinges on the
client side calling shutdown() on the socket. I don't know enough about
.net's internals to judge wether it does so. I've traced things far
enough to find
"Disposing a Stream object flushes any buffered
Am 23.01.2015 um 09:17 schrieb Abhijit Menon-Sen:
At 2014-06-03 22:30:50 -0400, pete...@gmx.net wrote:
I'm not sure whether the following coding actually detects any errors:
Solution.pm:
open(P, cl /? 21 |) || die cl command not found;
Since nobody with a Windows system has commented,
Hackers,
the attached patch enables Microsoft Visual Studio 2013 as additional
build environment.
After some tweaking (VS now has got its own rint and a few macro
definitions that were previously missing) the build runs without errors
or warnings and the product passes the regression tests.
I
On 01/23/2013 02:14 PM, Craig Ringer wrote:
How have you been testing VS2012 builds? In what environment?
When I tested this patch the last time I've been using Windows 8 RTM
(Microsoft Windows 8 Enterprise Evaluation - 6.2.9200 Build 9200) and
Microsoft Visual Studio Express 2012 für
Alvaro Herrera wrote:
There having been no updated patch yet, I have closed this as returned
with feedback. Thanks Noah!
Please make sure to submit an updated patch to the upcoming commitfest,
which is due to start in about three weeks.
Due to an hyperacute increase of workload in my day
Noah Misch wrote:
The only matter still requiring attention is a fix for IsoLocaleName().
Yep - I'll work on this and on some denoisifying of the build log files.
Regards,
Brar
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Noah Misch wrote:
My build log filled 8.8 MiB, a large increase from the 432 KiB of the chough
build log. This isn't strictly a problem, but do you happen to have ideas for
curbing the noise?
Not yet.
I find no functional problems with the patch, but some comment updates and
other trivia
Noah Misch wrote:
I decided to try a 32-bit build, but Solution::DeterminePlatform
detected it as x64. Its shibboleth is no longer valid; the cl.exe shipping
with VS 2012 Express for Desktop has a /favor option for both architectures:
32clhelp:/favor:blend|ATOM select processor to optimize
Noah Misch wrote:
I'm marking this patch Waiting on Author, but the changes needed to
get it Ready for Committer are fairly trivial. Thanks, nm
Thanks for your review and sorry for my delayed response - I've been on
vacation.
I'll look into adressing your comments and suggestions within
Heikki Linnakangas wrote:
I don't think we can realistically support VS2012 until Microsoft
releases the gratis Visual Studio Express 2012 for Windows Desktop.
As they've released now I've updated my Patch with docs and ask for review.
Regards,
Brar
diff -Napcdr -x .git
Magnus Hagander wrote:
I don't have too much hope for them actually changing it - they seem
hell-bent on forcing everybody into metro, and this seems to be yet
another way to do that. But we can always hope...
Looks like they've learnt their lesson...
The attached patch makes postgres build with Visual Studio 2012 RC.
As MS finally decided on the name I don't expect any need for changes
for the final RTM.
I didn't bother to update the docs for now as I still have some hope
that the developer community succeds in pushig M$ to reverse this
I'm currently doing some tests on range types:
tests=# SELECT int8range(5,15) * int8range(10,20) AS intersection;
intersection
--
[10,15)
(1 Zeile)
tests=#
tests=# SELECT '[2010-03-15,2010-05-22)'::daterange *
'[2010-01-04,)'::daterange AS intersection;
intersection
Misa Simic wrote:
I think result is ok... 2010-01-04 is not inside first range...
Staring at my query for five minutes obviously didn't prevent me from
creating that noise.
I meant to query SELECT '[2010-03-15,2010-05-22)'::daterange *
'[2010-04-01,)'::daterange AS intersection; which
Andrew Dunstan wrote:
Can you narrow down exactly what in that commit broke VS 2010? Are
there any compiler warnings?
I was able to nail down the problem.
Running the regression tests (vcregress check) gives the following messages:
snip
== creating temporary installation
Brar Piening wrote:
I have to admit that it's currently broken (it builds but fails during
regression tests becuse it can't connect) when building with Visual
Studio 2010 or Windows SDK 7.1 because of commit
1a0c76c32fe470142d3663dd84ac960d75a4e8db (Enable compiling with the
mingw-w64 32 bit
Andrew Dunstan wrote:
In the absence of reaction to this I've marked the patch as waiting
on author, but if/when I have time I'll work on rearranging things as
above.
Sorry for my non-reaction.
I'm currently trying to find some time window in my before chrismas
schedule but it seems like
Magnus Hagander wrote:
I'd vote for whatever matches the general perl pest practices at
this time.
I didn't kow the perl pest practices until now but as the PostgreSQL
community is more into C I think I know what you mean ;-)
--
Sent via pgsql-hackers mailing list
Andrew Dunstan wrote:
Some minor nitpicks:
Do we really need to create all those VSProject.pm and
VSSolution.pm files? They are all always included anyway. Why not
just stash all the packages in Solution.pm and Project.pm?
We certainly don't *need* them.
Having different files
Josh Berkus wrote:
Hackers,
Is there a reason why INTERVAL 'infinity' is not implemented? That is,
an interval which is larger than all defined intervals, and which added
to any timestamp turns it into 'infinity'.
Or is it just Round TUITs?
Probably the latter.
There is even a function
thready wrote:
[...]
I don't know how to apply this patch. What's the exe that runs this
patch? Will it ask me where the source folder root is when I run it?
As the archives seem to be unreachable at the moment I'm copying text
from the following message which I would otherwise ask you to
I use rss to follow up on patches that I'm interested in and it's the
second time I was wonering where my patch has gone in the commitfest app
due to $Topic.
Is this a known limitation?
If yes: Is there a way to change this?
If yes: Can/shall I help?
If yes: Where should I start?
Regards,
Brar Piening wrote:
I use rss to follow up on patches that I'm interested in and it's the
second time I was wonering where my patch has gone in the commitfest
app due to $Topic.
Just after pushing the send button my RSS-feed got updated and contained
the relevant information.
Sorry
Brar Piening wrote:
The attached patch includes documentation changes and excludes my
versions of pgbison.pl and pgflex.pl which have been replaced by
Andrews' versions that are already commited.
Building current head today I noticed that the patch doesn't apply
cleanly anymore.
Attached
Tom Lane wrote:
Putting a BOM into UTF8 data is flat out invalid per spec --- the fact
that Microsloth does it does not make it standards-conformant.
Could you share a pointer to the spec?
All I've ever heard is that a BOM is optional for UTF-8 but not forbidden.
The Unicode FAQ
Tom Lane wrote:
Yeah, that's a reasonable argument for rejecting the patch altogether.
I'm not qualified to decide whether it outweighs the we need to be able
to read Notepad output argument.
Actually it's not only notepad.
I quite often find myself doing something like the following when
Robert Haas wrote:
The thing that makes me doubt that is this comment from Tatsuo Ishii:
TI COPY explicitly specifies the encoding (to be UTF-8 in this case). So
TI I think we should not regard U+FEFF as BOM in COPY, rather we should
TI regard U+FEFF as ZERO WIDTH NO-BREAK SPACE.
If a BOM
Tom Lane wrote:
Note that the reference to byte order betrays the implicit context
assumption: that we're talking about UTF16 or UTF32 representation.
Note that there is no implicit context assumption in the Unicode FAQ.
It's equally covering UTF-8, UTF-16 and UTF-32.
Another quote:
Q: Can a
Brar Piening wrote:
It's a pity that the Unicode standard actually allows something that
can cause problems but blaming the non-platform again doesn't solve
the existing issues.
To put in a more humoruos but actually correct way:
M$ has found a standard conforming way of preventing users
Original Message
Subject: Re: [HACKERS] Review of VS 2010 support patches
From: Magnus Hagander mag...@hagander.net
To: Brar Piening b...@gmx.de
Date: 08.07.2011 11:38
Sorry for the late response - I've been on a wedding this weekend.
Something is strange here. Did you run
Original Message
Subject: Re: [HACKERS] Review of VS 2010 support patches
From: Craig Ringer cr...@postnewspapers.com.au
To: Brar Piening b...@gmx.de
Date: 07.07.2011 16:44
Frankly, I suggest leaving these tests for the buildfarm to sort out.
I don't see any sign of build
Original Message
Subject: Re: [HACKERS] Review of VS 2010 support patches
From: Craig Ringer cr...@postnewspapers.com.au
To: Brar Piening b...@gmx.de
Date: 06.07.2011 14:56
It turns out that VS2010v8.patch is also attached to the same message.
Not that you'd know it from
schrieb Andrew Dunstan:
Hmm, I missed that you had done this. Here are two replacement perl
scripts I knocked up, but haven't yet tested. One of the things about
them is that they remove knowledge of particular .l and .y files. and
instead get the required invocation options from the relevant
Original Message
Subject: Review of VS 2010 support patches
From: Craig Ringer cr...@postnewspapers.com.au
To: PG Hackers pgsql-hackers@postgresql.org, Brar Piening b...@gmx.de
Date: 05.07.2011 14:25
I haven't had any reply to my email to Brar, so there are a few
details
Original Message
Subject: Re: [HACKERS] %'ENV warnings during builds
From: Andrew Dunstan and...@dunslane.net
To: Brar Piening b...@gmx.de
Date: 05.07.2011 17:25
Try attached instead.
I can confirm that this version of pgflex.pl works as expected in my
environment
schrieb Craig Ringer:
I haven't managed to figure out exactly what's broken. For the benefit
of anyone else having problems like this or who might find this via a
search later, though: just install msys and use the current flex from
msys. It works perfectly in Pg's build environment and it's
schrieb Craig Ringer:
I'd appreciate it if you'd post the config.pl you're building with,
mainly so I can see what libraries and optional features you are or
are not using with your test builds.
I've already posted it here:
http://archives.postgresql.org/message-id/4dcda3cd.4030...@gmx.de
schrieb Magnus Hagander:
I think you've stumbled on just about all the bits of the MSVC build
system we haven't perlized. Maybe we should complete that task, and turn
clean.bat, pgbison.bat and pgflex.bat into pure one-line wrappers. (It was
done for builddoc just a few weeks ago).
Yeah, give
On Thu, 16 Jun 2011 22:49:45 +0300, Peter Eisentraut
pete...@gmx.net wrote:
This macro is provided by Autoconf and it appears to be using the
standard's terminology.
commit dbbba5279f66f95805c1e084e6f646d174931e56 refs/heads/master
Author: Peter Eisentraut pete...@gmx.net
Date: Thu Jun 16
be there for completeness
Robert Haas: We should be trying to put all types on equal footing,
rather than artificially privilege some over others.
Brar Piening (me): I'm with the above arguments. In addition I'd like
to mention that other databases have it too so having it improves
portability. Especially when
On Wed, 8 Jun 2011 19:29:42 -0400, Robert Haas
robertmh...@gmail.com wrote:
You should also change the status to either Waiting on Author or
Ready for Committer based on the content of the review. I think the
latter would be appropriate since your review seems to have been
favorable.
Well - not
On Wed, 20 Apr 2011 21:27:27 -0400, Mike Pultz m...@mikepultz.com wrote:
Can this be added?
Probably not - since it's not a complete patch ;-)
I tried to test this one but was unable to find a complete version of
the patch in my local mail archives and in the official archives
On Fri, 13 May 2011 23:34:05 +0200, Brar Piening b...@gmx.de wrote:
[...]
I'd appreciate any reviews, tests or comments.
As the current commitfest is getting more and more active recently i've
rechecked my patch and updated it for code drift.
No real changes.
See http://www.piening.info
On Sun, 06 Feb 2011 23:06:21 +0100, Brar Piening b...@gmx.de wrote:
On Sun, 30 Jan 2011 21:26:22 +0100, Magnus Hagander
mag...@hagander.net wrote:
it's not something we should hold up the CF / release for.
I agree.
At least it should get some more testing besides mine.
[...]
Being somewhat
On Fri, 13 May 2011 21:52:47 -0400, Robert Haas
robertmh...@gmail.com wrote:
You probably want to add it here, then:
https://commitfest.postgresql.org/action/commitfest_view/open
I's been in the last commitfest and i've recently moved it to the
current one already.
See
On Wed, 06 Apr 2011 22:07:52 +0200, Brar Piening b...@gmx.de wrote:
On Wed, 06 Apr 2011 20:04:37 +0200, Brar Piening b...@gmx.de wrote:
It's not ready yet but I'm prepared to get back to it as soon as
there's some serious interest.
I've updated the patch once again to reflect the fixes
On Wed, 11 May 2011 06:15:08 +0200, Brar Piening b...@gmx.de wrote:
I've updated the patch once again to reflect the fixes to pgbison.bat
in my alternative pgbison.pl
Actually not pgbison but pgflex
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Wed, 13 Apr 2011 10:45:25 +0200, Magnus Hagander
mag...@hagander.net wrote:
So per your experience, all we really need to do is to define what the
*max* level of the Windows SDK we can use is, to make sure people
don't get the VS2010 compiler instead?
(And adding the note that VS2010 isn't
On Tue, 12 Apr 2011 08:51:57 -0400, Andrew Dunstan
and...@dunslane.net wrote:
that's in the SDK? If not, I still think that should be our primary
option - I certainly don't see how it's obsolete. (and you can,
afaics, still get the platform sdk with the correct version of the
compiler
On Wed, 06 Apr 2011 20:27:22 +0300, Peter Eisentraut
pete...@gmx.net wrote:
I got it to build now. Here are is a list of notes that would make life
easier for future generations:
You might also want to have a look at my VS2010 patch as it already
touches some of those issues.
On Wed, 06 Apr 2011 20:04:37 +0200, Brar Piening b...@gmx.de wrote:
It's not ready yet but I'm prepared to get back to it as soon as
there's some serious interest.
I've rebased the patch in case somebody wants to try it.
http://www.piening.info/VS2010v5.patch
Regards,
Brar
--
Sent via
On Sun, 30 Jan 2011 21:26:22 +0100, Magnus Hagander
mag...@hagander.net wrote:
it's not something we should hold up the CF / release for.
I agree.
At least it should get some more testing besides mine.
I've set up virtual machines with VS 2003, VS 2005 Express, VS 2008
Express (+ my PC with
Hi,
I initially considered this patch as a primer to start off some basic
VS2010 support and not as something to be commited within the next few
commitfests.
As there seems to be at least some interest in this patch I refactored
the code and did some more testing (actually found some weird
On Tue, 18 Jan 2011 00:06:10 +0100, Brar Piening b...@gmx.de wrote:
So there is now a third version of this patch at
http://www.piening.info/VS2010v3.patch
Forgot to run perltidy on it - fixed in
http://www.piening.info/VS2010v4.patch
Sorry!
Brar
--
Sent via pgsql-hackers mailing list
Original-Nachricht
Datum: Mon, 3 Jan 2011 10:44:19 +0100
Von: Magnus Hagander mag...@hagander.net
An: Brar Piening b...@gmx.de
CC: pgsql-hackers@postgresql.org
Betreff: Re: [HACKERS] Visual Studio 2010/Windows SDK 7.1 support
This patch does not apply at all to my
/curl-ca-bundle.crt
sendemail.smtpserver=/bin/msmtp.exe
user.name=Brar Piening
user.email=[myemail]
core.repositoryformatversion=0
core.filemode=false
core.bare=false
core.logallrefupdates=true
core.symlinks=false
core.ignorecase=true
core.hidedotfiles=dotGitOnly
remote.origin.fetch=+refs/heads/*:refs
Hi,
i'v created a patch enables support for building PostgreSQL with Visual
Studio 2010 or Microsoft Windows SDK for Windows 7 and .NET Framework 4
(Windows SDK 7.1).
You can grab it from http://www.piening.info/VS2010.patch
It only touches the .pl, .pm and .bat files in src/tools/msvc so
On Tue, 1 Dec 2009 09:59:17 +0100, Dave Page dp...@pgadmin.org wrote:
I do see the argument that RESET ALL should revert user changes to
application_name though, but I maintain they should reset to the value
set at connection time, not to null. As has been pointed out already,
other values set
Josh Berkus wrote:
Having the contrib stuff in the main docs would remove one of the largest barriers
to people knowing about the contrib features.
Using PostgreSQL since Version 7.1.3 and reading this List since - I
dont't know exactly but my current archives start in 2003 which was the
Andrei Kovalevski schrieb:
I have an experience with writing ODBC driver for PostgreSQL
(https://projects.commandprompt.com/public/odbcng/). I would be happy
to help community to improve .NET data provider.
Please join the Npgsql Project at http://pgfoundry.org/projects/npgsql
Robert Treat schrieb:
That would be nice. Of course none of this seems relevant to hackers, so I'd
Your'e right - of course.
But sometimes I wish 'hackers' would care a little more about their
interfaces as the best backend can't be good without good interfaces and
some of the
62 matches
Mail list logo
