Tom Lane wrote:
"Dario V. Fassi" <[EMAIL PROTECTED]> writes:
SQL_ASCII is not an encoding (it's more like the absence of knowledge
about an encoding). What is the data actually stored as?
Yes you are right , the original data
Tom Lane wrote:
"Dario V. Fassi" <[EMAIL PROTECTED]> writes:
A simple question, we need to migrate many (>20) postgres databases from
SQL_ASCII encoding to UNICODE encoding, over a 7.3.6 server.
SQL_ASCII is not an encoding (it's more like
s the case the returning data type must be a floating point
data type like a double, but never 2 decimals for a row and 3, 4 or
whatever for others rows.
Stephan Szabo wrote:
On Sun, 4 Jul 2004, Dario V. Fassi wrote:
Stephan Szabo wrote:
On Sun, 4 Jul 2004, Kris Jurka
"coalesce", "case
then", etc.
The overflow or "data truncation" exception , for views, it's a going
back , but almost put the problem in programmer's hands.
Regards,
Dario.
Kris Jurka wrote:
On Sat, 3 Jul 2004, Dario V. Fassi wrote:
In th
Stephan Szabo wrote:
On Sun, 4 Jul 2004, Kris Jurka wrote:
On Sat, 3 Jul 2004, Dario V. Fassi wrote:
In the sample adjunct, you can see that error arise at the time when the
view's sql text is parsed and saved in database catalog.
Then generic NUMERIC ty
laboration for that.
Regards all,
Dario Fassi.
Dario V. Fassi wrote:
Kris Jurka wrote:
On Fri, 2 Jul 2004, Dario Fassi wrote:
Hi, I wish to report a erroneous information returned by
DatabaseMetaData.getColumns() method.
This happens with ResultSet&#
