Presumably, but that is not what I was doing.
I was taking a number from a user, which was supposed to be divisible by an
integer. Sometimes the user left off the last digit when typing in the
number or otherwise typed it in wrong, rendering the input not divisible by
that number.
So it was look
POSTGRESQL BUG REPORT TEMPLATE
Your name : Mike Martin
Your email address : [EMAIL PRO
POSTGRESQL BUG REPORT TEMPLATE
Your name : Mike Martin
Your email address : [EMAIL PROT
I would expect if I did intcol = 4.35 or intcol = 'abc', it would throw a
type mismatch error.
Now whether you want to be clever and make intcol = 4.0 not throw an error
and instead convert it to intcol = 4 is another thing. In that case, I
still wouldn't scan the table. And now that I think of
Hello
I tried create database with UNICODE encoding. When I try add row with
clasic czech text / yellow horse/ Příliš žluťoučký kůň se napil žluté
vody, I get following exception
invalid byte sequence for encoding "UNICODE": 0xf8ed6c
What is wrong? is it bog of npgsql-0.6rc3?
Thank You
Pavel
Hello
In my ASP.NET application I have problem with execution of
INSERT COMMAND with czech diacritics.
cn = New
NpgsqlConnection("Port=5432;Database=lrr;Server=triss.cesta;")
Dim cmd1 As New NpgsqlCommand("set client_encoding TO unicode", cn)
Dim cmd2 as New NpgsqlCommand("INSERT INTO
