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

problem with certain column names #84

Closed
qwesda opened this Issue Oct 8, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@qwesda

qwesda commented Oct 8, 2015

if you create the following table

CREATE TABLE "test" (
    "account_name" text
);

and then try to view it in postico, you get the following error message" Could not load table rows. The server said: column "account_name" does not exist.

On the command line everything works fine.

@qwesda

This comment has been minimized.

Show comment
Hide comment
@qwesda

qwesda Oct 8, 2015

Correction: it was an invisible character \ufeff.
This issue can be closed, but maybe the query editor should highlight characters like these.

qwesda commented Oct 8, 2015

Correction: it was an invisible character \ufeff.
This issue can be closed, but maybe the query editor should highlight characters like these.

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Oct 8, 2015

Owner
Owner

jakob commented Oct 8, 2015

@qwesda

This comment has been minimized.

Show comment
Hide comment
@qwesda

qwesda Oct 8, 2015

Thanks for fixing the issues! I only report them so that I'll have a good postgres client to work with!

It was a U+FEFF ZERO WIDTH NO-BREAK SPACE everybody's favourite invisible character. I got it from a tab separated file I was trying to import into postgres. The error was on my part not catching it, while I was transforming the header line into a create table statement, since sublime text also doesn't highlight these characters.

BBEDIT at least makes them look like a normal space (wich is better), but ideally the syntax highlighter should make these give them a coloured background and the width of a normal space.

I think you can't just remove things like these since they might be valid in an insert statement.

qwesda commented Oct 8, 2015

Thanks for fixing the issues! I only report them so that I'll have a good postgres client to work with!

It was a U+FEFF ZERO WIDTH NO-BREAK SPACE everybody's favourite invisible character. I got it from a tab separated file I was trying to import into postgres. The error was on my part not catching it, while I was transforming the header line into a create table statement, since sublime text also doesn't highlight these characters.

BBEDIT at least makes them look like a normal space (wich is better), but ideally the syntax highlighter should make these give them a coloured background and the width of a normal space.

I think you can't just remove things like these since they might be valid in an insert statement.

@jakob jakob added the started label Nov 22, 2015

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Nov 23, 2015

Owner

Byte order marks aka "ZERO WIDTH NO-BREAK SPACE" are now stripped when pasting text into the query view. If people really want to use that character in an insert statement, they'll have to use escape sequences.

Owner

jakob commented Nov 23, 2015

Byte order marks aka "ZERO WIDTH NO-BREAK SPACE" are now stripped when pasting text into the query view. If people really want to use that character in an insert statement, they'll have to use escape sequences.

@jakob jakob closed this Nov 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment