 |
|
 |
 |
|
 |
 |
| Author |
Message |
|
|
Post subject: Postgresql table script generation
Posted: Dec 22, 2004 - 04:00 AM
|
|
Veteran Member

Joined: Jul 23, 2003
Posts: 15
|
|
First off - you guys have done a wonderful job with the recent updates.
At my current assignment we use Postgresql 7.3.
When I use eclipse to generate table scripts - i get data types
such as int4(4) and int8(8)
Conversely - when using pgadmin-iii ( gui db tool ) the table scripts generated from this tool have data types
such as int4 and int8.
In addition - when I try to run scripts in eclipse - it fails on a parser error dealing with the parenthesis of int4(4).
These inconsistencies are causing a little bit of extra work - and I'm trying to conolidate things. I'd prefer to use eclipse - so if you have a suggestion I'm all ears.
Thanks for your help. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Dec 22, 2004 - 01:28 PM
|
|
Moderator


Joined: Jul 18, 2004
Posts: 357
|
|
| DE treats things pretty generically, and unfortunately some databases accept this syntax and others don't. All numerics get treated the same. I will look into some ways to resolve this, but for now the only work around is to edit the script that is generated to be syntactically correct (drop the precision and parens). |
_________________ jeff
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Aug 30, 2005 - 10:48 AM
|
|
Veteran Member


Joined: Jul 27, 2004
Posts: 3
|
|
It would be nice to have a way to set preferences for the generated scripts column data types.
Apart from that bug there is another. The table and column names are not quoted / escaped. If such a name is not acceptable (contains spaces, mixed case characters etc.), the script won't execute or will create the wrong table. Quoting should be fairly easy to add. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Sep 01, 2005 - 09:46 PM
|
|
Moderator


Joined: Aug 21, 2004
Posts: 1319
|
|
tt,
We are actually looking at this issue right now. I understand your point about table / column names and filed the request.
Could you give us an idea of the kind of preferences you would like for the data types?
We should be able to fix the int4(4) issue without user intervention or preference page; but perhaps you have some other preference ideas for different needs?
Best,
Brian. |
|
|
| |
|
|
|
 |
|
|
| |
|
|
 |
|
 |
|
|
|
 |