Re: [gnome-db] Column Type



Using Trunk Version 3222.

The table was created using the following SQL:

CREATE TABLE test (id serial primary key, description text);

With this function I get the following:

TABLE: test COLUMNS:
column_name | gtype      | data_type     
------------+------------+----------------
description | gchararray | pg_catalog.text
id          | gchararray | gint

The Query used to get this DataModel is:

SELECT column_name, gtype, data_type FROM _columns WHERE table_schema =  #schema::string AND table_catalog = ##catalog::string AND table_name = ##table::string


2008/10/1 Vivien Malerba <vmalerba gmail com>


2008/10/1 Daniel Espinosa <esodan gmail com>
I'm coding an application witch need column information type from a PostgreSQL provider, using V4.


When  I use gda-sql-4.0 I can see the following information:

List of columns for table 'prueba'
Column      | Type            | Nullable | Default                            |
Extra        
------------+-----------------+----------+------------------------------------+-
--------------
id          | gint            | no       | nextval('prueba_id_seq'::regclass) |
Auto increment
description | pg_catalog.text | yes      |


But whe I get the columns in a GdaMetaStore using
SELECT column_name, gtype \
                                                FROM _columns WHERE \
                                                table_schema = ##schema::string AND \
                                                table_catalog = ##catalog::string AND \
                                                table_name = ##table::string

for the same table 'prueba' in the same DB, when I dump to string the DataModel I got:

TABLE: prueba COLUMNS:
column_name | gtype    
------------+-----------
description | gchararray
id          | gchararray

The table type isn't the same using the different tools, why?

There surely is a bug somewhere... Can you tell me exactly which V4 version you use as I've recently corrected many small bugs regarding meta data? Also, if possible I'd appreciate if you could send me the ~/.libgda/gda-sql-<your DSN name>.db file which contains all the meta data for your database (or, if not possible, if you could send me a sample of the SQL you used to create the table which causes the problem) so I can reproduce the problem.

Cheers,

Vivien





--
Trabajar, la mejor arma para tu superación
"de grano en grano, se hace la arena" (R) (en trámite, pero para los cuates: LIBRE)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]