This is a discussion on character varying and specfying datatypes in pgadmin 1.6 within the pgsql Interfaces Pgadmin Support forums, part of the PostgreSQL category; --> Hello, Since new 1.6 beta there is no option to export database schema with "character varying" as "varchar". Wasn't ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, Since new 1.6 beta there is no option to export database schema with "character varying" as "varchar". Wasn't there such option in 1.5? It's removed now? Why it's not possible to use varchar in pgadmn dialogs anymore? Another annoying this is in Create table - >ADd Column dialog you cannot just type the desired datatype anymore, you're constricted to nearest match pgadmin finds for you. For example it's not possible to have "bigserial" datatype right away. After you type "big" it inserts bigint and you can't change it. The only way is to select it form list every time. (List is huge and not alphabetically sorted so you have to hunt for required datatype almost for every field) Thanks. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
| ||||
| On 17/10/06 13:39, "Joe Kramer" <cckramer@gmail.com> wrote: > Hello, > > Since new 1.6 beta there is no option to export database schema with > "character varying" as "varchar". Wasn't there such option in 1.5? > It's removed now? > > Why it's not possible to use varchar in pgadmn dialogs anymore? > PgAdmin 1.6 uses the SQL standard typenames rather than the PostgreSQL-specific ones. This is in line with the PostgreSQL utilities such as pg_dump and psql. > > Another annoying this is in Create table - >ADd Column dialog you > cannot just type the desired datatype anymore, you're constricted to > nearest match pgadmin finds for you. > For example it's not possible to have "bigserial" datatype right away. > After you type "big" it inserts bigint and you can't change it. The > only way is to select it form list every time. (List is huge and not > alphabetically sorted so you have to hunt for required datatype almost > for every field) > Hmm, seems to be a Mac-ism. The wx team changed the behaviour of the combo boxes in 2.6.2 (iirc), and we had to rewrite a bunch of code to fix things up. I wonder if we missed this brokeness on Mac, or whether they changed things again. Išll look into it. Thanks, Dave. |