[go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSSQL to PGSQL table and field names case insensitive #1597

Open
4 tasks done
Triskae opened this issue Jul 19, 2024 · 1 comment
Open
4 tasks done

MSSQL to PGSQL table and field names case insensitive #1597

Triskae opened this issue Jul 19, 2024 · 1 comment

Comments

@Triskae
Copy link
Triskae commented Jul 19, 2024

Hello guys, I'm trying to migrate all data from MSSQL to PGSQL, everything works fine, the data is migrated.

The problem is I don't understand why the case is not respected, for example if I have a table named MailType in source database, I expected pgloader to create the table with same name. Instead, it creates indeed the table, but named "mailtype".

Anyone knows how to get over it ?

Thanks a lot

  • pgloader --version

       pgloader version "3.6.9"
       compiled with SBCL 2.3.8
    
  • did you test a fresh compile from the source tree?

Nop, not tried, but does not seem to be a bug, I'm probably missing some config.

  • did you search for other similar issues?

  • [X ] how can I reproduce the bug?
    simply try to migrate from mssql to pgsql. In source database some tables need to be name with pascal case like "MailType"

LOAD DATABASE
    FROM mssql://username:password@localhost/source-db-name
    INTO pgsql://username:passwordlocalhost/destination-db-name
  • How the data is different from what you expected, if relevant

I'm expecting to have in the destination database, the table created with the exact same name as in source database, in this case "MailType" instead of "mailtype"

@Triskae Triskae changed the title MSSQL to PGSQL case no respected MSSQL to PGSQL table and field names case insensitive Jul 22, 2024
@Triskae
Copy link
Author
Triskae commented Jul 26, 2024

Up ? As anyone any info about this issue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant