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

SQL Export of BIT fields is broken in 1.1 #2262

Closed
dmoagx opened this issue Oct 3, 2015 · 4 comments
Closed

SQL Export of BIT fields is broken in 1.1 #2262

dmoagx opened this issue Oct 3, 2015 · 4 comments
Labels
Milestone

Comments

@dmoagx
Copy link
Member

dmoagx commented Oct 3, 2015

(This is a different issue than #2254)

SQL-Export:

INSERT INTO `bits` (`id`, `bitf`)
VALUES
    (1,001),
    (2,000),
    (3,101),
    (4,010),
    (6,111),
    (8,011);

This format is syntactically wrong and will by MySQL interpreted as decimal numbers with leading zeros.
It should have been either b'001',b'101', and so on... or the real decimal values.

@hcouplet
Copy link

hcouplet commented Oct 5, 2015

got the same issue with 1.1 where an export of a BIT(1) column was exported as 0000000.
Downgraded to 1.0.2 and everything was fine.

@robertoschwald
Copy link

Same issue here. But we can't use 1.0.2, as we are on El Capitan and ssh connections do not work with 1.0.2. Hope we get a new release asap.

@robertoschwald
Copy link

Works with nightly. Thanks for the fix.

@dmoagx
Copy link
Member Author

dmoagx commented Feb 20, 2016

Issue fixed in 1.1.1
See http://www.sequelpro.com/blog/2016.02/sequel-pro-1-1-1/

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

No branches or pull requests

3 participants