Re: 7.3 -> pg_atoi: zero-length string

That's indeed very nice but I don't see the logic in it.

If I want to upgrade I need to go on all my projects and change thousands of
lines.

And that's not all :(
I have other applications like phprojekt that was not developed by me and
became useless now as I cant insert.

Was this step so necessary ?

----- Original Message -----
From: "Lee Kindness" <lkindness@csl.co.uk>
To: "Ben-Nes Michael" <miki@canaan.co.il>
Cc: "postgresql" <pgsql-general@postgresql.org>; "Lee Kindness"
<lkindness@csl.co.uk>
Sent: Tuesday, December 03, 2002 12:37 PM
Subject: [GENERAL] 7.3 -> pg_atoi: zero-length string


> Hi, one of the changes in 7.3 was to disallow '' being implicitly
> converted to 0. In your example below image_order is clearly not a
> text/char column, so what are you trying to set it too? If you want it
> be 0 then explicitly use 0, if you want it to be undefined then use
> NULL.
>
> Lee.
>
> Ben-Nes Michael writes:
>  > Hi
>  >
>  > After I upgraded 7.2.3 to 7.3 I started to get the following errors:
>  > pg_atoi: zero-length string
>  >
>  > its seems that i get it when not all field have content:
>  >
>  > this is one example that generate the error:
>  > insert into images (section_id, pic_date, image_order) values ('8',
>  > '2002-12-03', '')
>  >
>  >
>  > ---------------------------(end of
broadcast)---------------------------
>  > TIP 2: you can get off all lists at once with the unregister command
>  >     (send "unregister YourEmailAddressHere" to
majordomo@postgresql.org)
>