Dump MySQL table to csv file (utf8mb4_unicode_ci)





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I have MySQL table with columns (character-set: utf8, collation: utf8mb4_unicode_ci) to be exported to a .csv file.



mysqldump -u *** -p -t -T/tmp/ dbname tablename --default-character-set=utf8mb4


The output has more lines than the records in the table due to some symbols? characters? to break the lines incorrectly. (see pics below) Adding "enclosed by" or "escaped by" do not help.



column



output










share|improve this question














bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Did you have your problem solved?

    – joanolo
    Apr 2 '17 at 11:08


















0















I have MySQL table with columns (character-set: utf8, collation: utf8mb4_unicode_ci) to be exported to a .csv file.



mysqldump -u *** -p -t -T/tmp/ dbname tablename --default-character-set=utf8mb4


The output has more lines than the records in the table due to some symbols? characters? to break the lines incorrectly. (see pics below) Adding "enclosed by" or "escaped by" do not help.



column



output










share|improve this question














bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Did you have your problem solved?

    – joanolo
    Apr 2 '17 at 11:08














0












0








0








I have MySQL table with columns (character-set: utf8, collation: utf8mb4_unicode_ci) to be exported to a .csv file.



mysqldump -u *** -p -t -T/tmp/ dbname tablename --default-character-set=utf8mb4


The output has more lines than the records in the table due to some symbols? characters? to break the lines incorrectly. (see pics below) Adding "enclosed by" or "escaped by" do not help.



column



output










share|improve this question














I have MySQL table with columns (character-set: utf8, collation: utf8mb4_unicode_ci) to be exported to a .csv file.



mysqldump -u *** -p -t -T/tmp/ dbname tablename --default-character-set=utf8mb4


The output has more lines than the records in the table due to some symbols? characters? to break the lines incorrectly. (see pics below) Adding "enclosed by" or "escaped by" do not help.



column



output







mysql mysqldump table export csv






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 15 '17 at 22:11









user117624user117624

1




1





bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Did you have your problem solved?

    – joanolo
    Apr 2 '17 at 11:08



















  • Did you have your problem solved?

    – joanolo
    Apr 2 '17 at 11:08

















Did you have your problem solved?

– joanolo
Apr 2 '17 at 11:08





Did you have your problem solved?

– joanolo
Apr 2 '17 at 11:08










1 Answer
1






active

oldest

votes


















0














The CSV "de facto standard" allows for fields to contain line breaks. So, what you get is the result of some of your data in your original table containing line breaks.



When that's the case, one record uses more than one row of text.



Some libraries or some programs can handle and interpret that adequately, but not all do. For instance, you can use MS Access, and it will work; but if you try MS Excel, line breaks within a field won't be properly handled. If you work with MySQL or PostgreSQL, they can import/export CSV with line breaks in fields.



Check, for instance, Comma-separated values at WikiPedia or RFC 4180




Fields with embedded line breaks must be quoted (however, many CSV implementations do not support embedded line breaks).







share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f164482%2fdump-mysql-table-to-csv-file-utf8mb4-unicode-ci%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The CSV "de facto standard" allows for fields to contain line breaks. So, what you get is the result of some of your data in your original table containing line breaks.



    When that's the case, one record uses more than one row of text.



    Some libraries or some programs can handle and interpret that adequately, but not all do. For instance, you can use MS Access, and it will work; but if you try MS Excel, line breaks within a field won't be properly handled. If you work with MySQL or PostgreSQL, they can import/export CSV with line breaks in fields.



    Check, for instance, Comma-separated values at WikiPedia or RFC 4180




    Fields with embedded line breaks must be quoted (however, many CSV implementations do not support embedded line breaks).







    share|improve this answer




























      0














      The CSV "de facto standard" allows for fields to contain line breaks. So, what you get is the result of some of your data in your original table containing line breaks.



      When that's the case, one record uses more than one row of text.



      Some libraries or some programs can handle and interpret that adequately, but not all do. For instance, you can use MS Access, and it will work; but if you try MS Excel, line breaks within a field won't be properly handled. If you work with MySQL or PostgreSQL, they can import/export CSV with line breaks in fields.



      Check, for instance, Comma-separated values at WikiPedia or RFC 4180




      Fields with embedded line breaks must be quoted (however, many CSV implementations do not support embedded line breaks).







      share|improve this answer


























        0












        0








        0







        The CSV "de facto standard" allows for fields to contain line breaks. So, what you get is the result of some of your data in your original table containing line breaks.



        When that's the case, one record uses more than one row of text.



        Some libraries or some programs can handle and interpret that adequately, but not all do. For instance, you can use MS Access, and it will work; but if you try MS Excel, line breaks within a field won't be properly handled. If you work with MySQL or PostgreSQL, they can import/export CSV with line breaks in fields.



        Check, for instance, Comma-separated values at WikiPedia or RFC 4180




        Fields with embedded line breaks must be quoted (however, many CSV implementations do not support embedded line breaks).







        share|improve this answer













        The CSV "de facto standard" allows for fields to contain line breaks. So, what you get is the result of some of your data in your original table containing line breaks.



        When that's the case, one record uses more than one row of text.



        Some libraries or some programs can handle and interpret that adequately, but not all do. For instance, you can use MS Access, and it will work; but if you try MS Excel, line breaks within a field won't be properly handled. If you work with MySQL or PostgreSQL, they can import/export CSV with line breaks in fields.



        Check, for instance, Comma-separated values at WikiPedia or RFC 4180




        Fields with embedded line breaks must be quoted (however, many CSV implementations do not support embedded line breaks).








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 15 '17 at 22:54









        joanolojoanolo

        9,95842254




        9,95842254






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f164482%2fdump-mysql-table-to-csv-file-utf8mb4-unicode-ci%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Liste der Baudenkmale in Friedland (Mecklenburg)

            Single-Malt-Whisky

            Czorneboh