Unfortunately, the statement doesn't work. I get an error message about unable
to convert boolean to integer.
I have a look at the case statement for the conversion, but don't understand
how it works.
- Original Message -
From: "Arjen Nienhuis"
To: wei...@lycos.com
Cc: pgsql-general@
That shall work. I assume that 0 - false, 1 - true.
Thank everyone for your suggestion.
- Original Message -
From: "Arjen Nienhuis"
To: wei...@lycos.com
Cc: pgsql-general@postgresql.org
Sent: Thursday, August 26, 2010 4:56:09 AM GMT -08:00 US/Canada Pacific
Subject: Re: [GENERAL] How to
You are right. I typed the message in hurry before I left home this morning. It
is the boolean type. Thanks for your suggestion. The NULL value may not work
for jdbc. On the application level, a fixed set of constants is used to
represent the three status, which are converted into an integer.
I have an application in the product. Now, one status field needs to have three
statuses instead of two. How to make a such change in PostgreSQL?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-
About four five years ago, I had received a few of emails about the data type
problems on this mailing list. I believe that the problem was about a
performance issue. Is any problem withe the Long Integer type in the late
releases?
Thanks,
- w
--
Sent via pgsql-general mailing list (pgsql-g