pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: [INTERFACES] why there's only char type?
5+ messages / 2 participants
[nested] [flat]
* why there's only char type?
@ 1999-03-23 00:16 Daniel <daniel@ids.org.my>
1999-03-22 19:14 ` Re: [INTERFACES] why there's only char type? Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 5+ messages in thread
From: Daniel @ 1999-03-23 00:16 UTC (permalink / raw)
To: pgsql-interfaces@hub.org
Last week I got PostgreSQL 6.3.x running with -i switch and then created a
test database. On Win95 end, postODBC was installed and my PowerBuilder
could connect to the database. Then I tried to transfer the data from Sybase
SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
Powerbuilder I did notice that there were some unfamiliar database type in
Postgres such as INT4 to represent Sybase's INTEGER type and got me really
excited. However I couldnt create anything in Postgres because I forgot to
uncheck the "read-only" option when i setup the odbc connection, but that's
different story.
After coming back from weekend, I tried to do the transfer of data again,
and I did make sure the "read-only" option has been unchecked. But right now
I encounter a new problem: I found that I could no longer see other data
type in Postgres except CHAR. I've tried all the possible setting in odbc
connection but it still doesn't help. What seems to be the problem? Please
help.
Daniel
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [INTERFACES] why there's only char type?
1999-03-23 00:16 why there's only char type? Daniel <daniel@ids.org.my>
@ 1999-03-22 19:14 ` Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 5+ messages in thread
From: Byron Nikolaidis @ 1999-03-22 19:14 UTC (permalink / raw)
To: Daniel <daniel@ids.org.my>; +Cc: pgsql-interfaces@hub.org
Daniel wrote:
> Last week I got PostgreSQL 6.3.x running with -i switch and then created a
> test database. On Win95 end, postODBC was installed and my PowerBuilder
> could connect to the database. Then I tried to transfer the data from Sybase
> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
> Powerbuilder I did notice that there were some unfamiliar database type in
> Postgres such as INT4 to represent Sybase's INTEGER type and got me really
> excited. However I couldnt create anything in Postgres because I forgot to
> uncheck the "read-only" option when i setup the odbc connection, but that's
> different story.
>
> After coming back from weekend, I tried to do the transfer of data again,
> and I did make sure the "read-only" option has been unchecked. But right now
> I encounter a new problem: I found that I could no longer see other data
> type in Postgres except CHAR. I've tried all the possible setting in odbc
> connection but it still doesn't help. What seems to be the problem? Please
> help.
>
I'm not sure why you would only see 'char'. If the application is using the
odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
looking for data types that support a certain feature. Maybe this is
configurable. I'm not really sure what your application is doing.
If you want, you could send an odbc trace log of the session so we could at
least see if it is calling SQLGetTypeInfo() and retrieving the results.
Otherwise, there is nothing else I can do.
Byron
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [INTERFACES] why there's only char type?
@ 1999-03-24 23:15 Daniel <daniel@ids.org.my>
0 siblings, 0 replies; 5+ messages in thread
From: Daniel @ 1999-03-24 23:15 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces@hub.org
After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.
Anyway, thanks for suggesting looking into the log file. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).
If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.
Daniel
-----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:35 AM
Subject: Re: [INTERFACES] why there's only char type?
>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'. If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature. Maybe this is
>configurable. I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>
>
Attachments:
Sql.log (application/octet-stream, 156.2K) download
psqlodbc.log (application/octet-stream, 4.9K) download
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [INTERFACES] why there's only char type?
@ 1999-03-25 00:03 Daniel <daniel@ids.org.my>
1999-03-24 14:24 ` Re: [INTERFACES] why there's only char type? Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 5+ messages in thread
From: Daniel @ 1999-03-25 00:03 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces@hub.org
After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.
Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).
If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.
Daniel
-----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?
>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'. If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature. Maybe this is
>configurable. I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>
Attachments:
Sql.log (application/octet-stream, 6.2K) download
psqlodbc.log (application/octet-stream, 4.9K) download
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [INTERFACES] why there's only char type?
1999-03-25 00:03 Re: [INTERFACES] why there's only char type? Daniel <daniel@ids.org.my>
@ 1999-03-24 14:24 ` Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 5+ messages in thread
From: Byron Nikolaidis @ 1999-03-24 14:24 UTC (permalink / raw)
To: Daniel <daniel@ids.org.my>; +Cc: pgsql-interfaces@hub.org
Daniel wrote:
> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>
The below excerpt from the log I think reveals the problem. You are using an older version
of the driver (according to the psqlodbc.log -- Version='06.30.0250') that does not support
setting the rowset size to anything greater than 1. You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050 fffb7063:fffc2b73 ENTER
SQLGetTypeInfo HSTMT 0x013a0d44
SWORD 0 <SQL_ALL_TYPES>
PB050 fffb7063:fffc2b73 EXIT SQLGetTypeInfo with return code 0 (SQL_SUCCESS)
HSTMT 0x013a0d44
SWORD 0 <SQL_ALL_TYPES>
PB050 fffb7063:fffc2b73 ENTER SQLSetStmtOption
HSTMT 0x013a0d44
UWORD 9 <SQL_ROWSET_SIZE>
UDWORD 16
PB050 fffb7063:fffc2b73 EXIT SQLSetStmtOption with return code 1
(SQL_SUCCESS_WITH_INFO)
HSTMT 0x013a0d44
UWORD 9 <SQL_ROWSET_SIZE>
UDWORD 16
DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)
, fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
disable_optimizer=1, unique_index=0, use_declarefetch=0
text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
extra_systable_prefixes='dd_;', conn_settings=''
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~1999-03-25 00:03 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-03-23 00:16 why there's only char type? Daniel <daniel@ids.org.my>
1999-03-22 19:14 ` Byron Nikolaidis <byronn@insightdist.com>
1999-03-24 23:15 Re: [INTERFACES] why there's only char type? Daniel <daniel@ids.org.my>
1999-03-25 00:03 Re: [INTERFACES] why there's only char type? Daniel <daniel@ids.org.my>
1999-03-24 14:24 ` Byron Nikolaidis <byronn@insightdist.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox