Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pGMfW-000237-3I for pgsql-general@arkaria.postgresql.org; Fri, 13 Jan 2023 16:12:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pGMfU-0000Yh-0w for pgsql-general@arkaria.postgresql.org; Fri, 13 Jan 2023 16:12:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pGMfT-0000YX-L9 for pgsql-general@lists.postgresql.org; Fri, 13 Jan 2023 16:12:35 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pGMfQ-0006b2-Kq for pgsql-general@lists.postgresql.org; Fri, 13 Jan 2023 16:12:34 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-4c24993965eso284926237b3.12 for ; Fri, 13 Jan 2023 08:12:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:from:content-language:to:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=LeY6/phmcDR8YIQ/bbvNeYm6Rq6uTtF28xHP3aMQP78=; b=bVfMZpuSNEUePRu4CzLFDhzfCqL0BJJXO4hw5I2uL1GuI2rIHT3JVbMkHohID/D/Bi QfwnKVKU4iEkDHMr/bQ4Bi+oYRzTEPMQjzO/30PUPyLshy4nfvRGWxYkwdmI1K5djmo+ WvGR7+pppF/iY9co8nPJHic4yI7m5FWfouU4hJqYFoXmmoH57NmxU+lOSn/J+hVLHGts NMInZX1tNQ196iiZ7PPul5a6jsjNlP2xOiidVAvlkbGPAFsQAMmjp+xDHpao25wDValI uNdKWpVccE8uD1Tizz9HnyD+joseTbUWD+mCojA9wlCqYGXj1x/gAYC73oJim2IqkxZK YTWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=subject:from:content-language:to:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LeY6/phmcDR8YIQ/bbvNeYm6Rq6uTtF28xHP3aMQP78=; b=O4A1D6gLIGWJ82lkseSZtvI3nC7ZHmLdyVAZ47MDe/vDevXrDgsbVqyxANS5pL6Nx2 BTtQDfjzPTC+Xb44kypWNKpPKptaR2/UBm35dAHiMtB0qSQciuk/eu+yJnjodxUZYWcG KeGEKpUpqKepO7sux0GQgFQF2Ly7SGr7OBbfVQJrCuKuwociE7TvyWfS/bogmbSgA2ki MhRyYXNxqHUWhZt+dvcXcbs9QR2uWSlX00n3KDPVdPMwPto3alrghu6dzBVX1QQo16M/ +d0FQGzE1zrcp5CArfm3uMkxM1CbP7rSz5O8jJ1n2tZFKddHozK+BBdlbZNBx0/I8oPL V8nA== X-Gm-Message-State: AFqh2kq7dd/RNbUOabPipbleBXH8dY9a0irRq6PboyZBGop8J3A8xn1G alvKO7q2JqhUGEFmJR4X0EiKPV8xCAlcEQ== X-Google-Smtp-Source: AMrXdXuwE+fD5V2OjYfGkua99SKdXtajKflZHoqEh3NVSOCq8PjuxGOq4bdbwSIMs1D2BMWShc0SQA== X-Received: by 2002:a05:7500:c88:b0:f0:5d43:850 with SMTP id fu8-20020a0575000c8800b000f05d430850mr917952gab.58.1673626351500; Fri, 13 Jan 2023 08:12:31 -0800 (PST) Received: from [192.168.1.66] (108-250-206-84.lightspeed.nworla.sbcglobal.net. [108.250.206.84]) by smtp.googlemail.com with ESMTPSA id do1-20020a05620a2b0100b00706284b74b5sm607685qkb.52.2023.01.13.08.12.31 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Jan 2023 08:12:31 -0800 (PST) Content-Type: multipart/alternative; boundary="------------Soxy6be9l1alaYolRYBhOY2F" Message-ID: Date: Fri, 13 Jan 2023 10:12:30 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 To: "pgsql-general@lists.postgresql.org" Content-Language: en-US From: Ron Subject: Directly embedding a psql SET variable inside another string? List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Soxy6be9l1alaYolRYBhOY2F Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Pg 12 I need to pass a \set variable (in this example named v_ssn) into a LIKE string.  A two-stage process (building v_like from v_ssn, and then using v_like in the LIKE string) works, and is fine when executing an sql script, but not so good  is there any way to *directly* embed v_ssn in another string? test=# \set v_ssn 345 test=# \echo :v_ssn 345 test=# \set v_like %:v_ssn% test=# \echo :v_like %345% test=# SELECT * FROM employee WHERE ssn LIKE :'v_like';     ssn    |   name   |  ssn_int -----------+----------+-----------  123456789 | John Doe | 123456789 (1 row) As expected, this fails: postgres=# SELECT * FROM employee WHERE ssn LIKE :'%v_ssn%'; ERROR:  syntax error at or near ":" LINE 1: SELECT * FROM employee WHERE ssn LIKE :'%v_ssn%'; -- Born in Arizona, moved to Babylonia. --------------Soxy6be9l1alaYolRYBhOY2F Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Pg 12

I need to pass a \set variable (in this example named v_ssn) into a LIKE string.  A two-stage process (building v_like from v_ssn, and then using v_like in the LIKE string) works, and is fine when executing an sql script, but not so good  is there any way to directly embed v_ssn in another string?

test=# \set v_ssn 345
test=# \echo :v_ssn
345
test=# \set v_like %:v_ssn%
test=# \echo :v_like
%345%

test=# SELECT * FROM employee WHERE ssn LIKE :'v_like';
    ssn    |   name   |  ssn_int  
-----------+----------+-----------
 123456789 | John Doe | 123456789
(1 row)

As expected, this fails:

postgres=# SELECT * FROM employee WHERE ssn LIKE :'%v_ssn%';
ERROR:  syntax error at or near ":"
LINE 1: SELECT * FROM employee WHERE ssn LIKE :'%v_ssn%';


--
Born in Arizona, moved to Babylonia.
--------------Soxy6be9l1alaYolRYBhOY2F--