On Thu, Oct 7, 2010 at 00:00, Craig Ringer wrote:
> On 05/10/10 16:08, Mike Christensen wrote:
>
>> at Npgsql.NpgsqlCommand.CheckConnectionState() at
>> Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb) at
>
> It looks like nobody reading -GENERAL really speaks npgsql/.NET/C#.
> Perhaps you sh
On 05/10/10 16:08, Mike Christensen wrote:
>at Npgsql.NpgsqlCommand.CheckConnectionState() at
> Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb) at
It looks like nobody reading -GENERAL really speaks npgsql/.NET/C#.
Perhaps you should try on the npgsql list instead?
Try filing a bug/suppor
Hey I know most of you guys are huge Windows fans, and UNIX support
will eventually be dropped in Postgres cuz really who uses that, but I
figure someone in here would love to help me with a Windows issue that
has me confused.
Postgres is working awesome on my Windows 2003 development
environment,
