In PostGreSQL should the back references of a regexp_replace work in a CASE statement?












0















Example (the ELSE always gets chosen):



SELECT regexp_replace('ABCDEFG','(C)(D)', CASE WHEN '1' = 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG

SELECT regexp_replace('ABCDEFG','(C)(D)', CASE '1' WHEN 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG


Is there a way to make this work?










share|improve this question























  • It seems the '1' in the WHEN is a literal and not a back-reference but the result in the THEN can contain back-references. I am using PostGres 9.4.

    – Pete
    Nov 19 '18 at 22:27


















0















Example (the ELSE always gets chosen):



SELECT regexp_replace('ABCDEFG','(C)(D)', CASE WHEN '1' = 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG

SELECT regexp_replace('ABCDEFG','(C)(D)', CASE '1' WHEN 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG


Is there a way to make this work?










share|improve this question























  • It seems the '1' in the WHEN is a literal and not a back-reference but the result in the THEN can contain back-references. I am using PostGres 9.4.

    – Pete
    Nov 19 '18 at 22:27
















0












0








0








Example (the ELSE always gets chosen):



SELECT regexp_replace('ABCDEFG','(C)(D)', CASE WHEN '1' = 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG

SELECT regexp_replace('ABCDEFG','(C)(D)', CASE '1' WHEN 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG


Is there a way to make this work?










share|improve this question














Example (the ELSE always gets chosen):



SELECT regexp_replace('ABCDEFG','(C)(D)', CASE WHEN '1' = 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG

SELECT regexp_replace('ABCDEFG','(C)(D)', CASE '1' WHEN 'C' THEN '+21+' ELSE '-12-' END);
**returns =>** AB-CD-EFG


Is there a way to make this work?







regex postgresql switch-statement






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 '18 at 21:42









PetePete

34036




34036













  • It seems the '1' in the WHEN is a literal and not a back-reference but the result in the THEN can contain back-references. I am using PostGres 9.4.

    – Pete
    Nov 19 '18 at 22:27





















  • It seems the '1' in the WHEN is a literal and not a back-reference but the result in the THEN can contain back-references. I am using PostGres 9.4.

    – Pete
    Nov 19 '18 at 22:27



















It seems the '1' in the WHEN is a literal and not a back-reference but the result in the THEN can contain back-references. I am using PostGres 9.4.

– Pete
Nov 19 '18 at 22:27







It seems the '1' in the WHEN is a literal and not a back-reference but the result in the THEN can contain back-references. I am using PostGres 9.4.

– Pete
Nov 19 '18 at 22:27














1 Answer
1






active

oldest

votes


















0














No it shouldn't.



I would use regexp_match with groups for the stuff before C and after D as well, and then construct the result from the matched parts using CASE and concatenation.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f53383060%2fin-postgresql-should-the-back-references-of-a-regexp-replace-work-in-a-case-stat%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














    No it shouldn't.



    I would use regexp_match with groups for the stuff before C and after D as well, and then construct the result from the matched parts using CASE and concatenation.






    share|improve this answer




























      0














      No it shouldn't.



      I would use regexp_match with groups for the stuff before C and after D as well, and then construct the result from the matched parts using CASE and concatenation.






      share|improve this answer


























        0












        0








        0







        No it shouldn't.



        I would use regexp_match with groups for the stuff before C and after D as well, and then construct the result from the matched parts using CASE and concatenation.






        share|improve this answer













        No it shouldn't.



        I would use regexp_match with groups for the stuff before C and after D as well, and then construct the result from the matched parts using CASE and concatenation.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 19 '18 at 22:29









        Alexey BashtanovAlexey Bashtanov

        38435




        38435






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • 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%2fstackoverflow.com%2fquestions%2f53383060%2fin-postgresql-should-the-back-references-of-a-regexp-replace-work-in-a-case-stat%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

            android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

            SQL update select statement

            'app-layout' is not a known element: how to share Component with different Modules