Re: bug?

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "gary" <gary(at)virtrail(dot)com>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: bug?
Date: 2004-01-11 10:48:08
Message-ID: 03AF4E498C591348A42FC93DEA9661B87203E1@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi Gary,

> -----Original Message-----
> From: gary [mailto:gary(at)virtrail(dot)com]
> Sent: 10 January 2004 05:05
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] bug?
>
> hi,
> i have succesfully migrated the MSSQL database to
> postgresql using the database migration wizard of pgadmin. is
> there a way to disable the naming modification during the
> migration process.
> .for example, all the foreign key is append with the string
> '_fk' .

No, I'm afraid this is not possible unless you can modify the code
yourself.

> And one thing i notice is that if my MSSQL index name
> contain the string 'name' eg IX_UC_Community_name, migration
> will rename it to IX_UC_Community_-0

The algorithm actually creates the name as:

<tablename>_<indexname>_idx-<num>

However the <tablename>_<indexname> section is truncated to a maximum of
26 characters. There are various historical reasons for this - mainly it
is to ensure that the name is both unique across the database, not too
long (for older versions of PostgreSQL), and vaguely useful. Again
though, you cannot modify this behaviour without changing the code.

> great software though!

Thanks!

Regards, Dave.

Browse pgadmin-support by date

  From Date Subject
Next Message Błażej 2004-01-12 08:44:24 Error Message: ERROR: Relation "pg_cast" does not exist
Previous Message gary 2004-01-10 05:05:05 bug?