quoting

I've got a probably very simple issue to which I can't find a satisfactory (subjectively seen) answer in the Zend Framework manual or elsewhere... There are so many ways how I can hand over my php variables to my sql queries that I lost the overview and probably I lack some understanding about quoting in general. Prepared Statements $sql = "SELECT this, that FROM table WHERE id = ? AND restriction = ?"; $stmt = $this->_db->query($sql, array($myId, $myValue)); $result = $stmt->fetchAll(); I understand that with this solution I don't need to quote anything because the db handles this for me.

I have looked at this question , but it does not cover my use case. Suppose I have the variable foo which holds the four-character literal \x60 . I want to perform ANSI C Quoting on the contents of this variable and store it into another variable bar . I tried the following, but none of them achieved the desired effect. bar=$'$foo' echo $bar bar=$"$foo" echo $bar Output: $foo \x61 Desired output (actual value of \x61 ): a How might I achieve this in the general case, including non-printable characters? Note that in this case a was used just as an example to make it easier to test whether the

So I have a problem below, but my question is more generic - how to see exact content of memory referenced by bash variable to understand why they don't match: # [[ $c1 == $c ]] || echo nope nope # [[ $c1 == "bkup dt" ]] || echo nope # [[ $c == "bkup dt" ]] || echo nope nope # hexdump -C <<<$c 00000000 62 6b 75 70 20 64 74 0a |bkup dt.| 00000008 # hexdump -C <<<$c1 00000000 62 6b 75 70 20 64 74 0a |bkup dt.| 00000008 # [ "$c1" = "$c" ] || echo nope nope # [ ! "$c1" = "$c" ] || echo nope Or does it look like a bug? I can repeat the problem with: $ cd /tmp $ mkdir aaa $ echo 2 > aaa/1 $ echo 2 >

I googled a lot but.. How do I escape single quote in command line query of psql ? psql -t -A -F $'\t' postgresql://zzzz:5432/casedb -U qqqq -c 'select id,ext_ids ->> 'qwe' as qwe from data ORDER BY qwe' > /jdata/qwe.tab Results in error ERROR: column "qwe" does not exist LINE 1: select id,ext_ids ->> qwe as qwe from data... In Postgres you can use dollar-quoted strings : select id,ext_ids ->> $$qwe$$ as qwe from data ORDER BY qwe; -- or select id,ext_ids ->> $anything$qwe$anything$ as qwe from data ORDER BY qwe; You could just use double quotes ( " ) for the shell quoting and single quotes (

I'm trying this $Global:commandBlock={ Start-Transcript -path $projectFolder\gruntLog.txt; grunt $argList; Stop-Transcript } $cmdProc=start-process powershell -ArgumentList ('-command `$Global:commandBlock') -WorkingDirectory $fwd -PassThru -NoNewWindow:$NoNewWindow And keep getting $commandBlock : The term '$Global:commandBlock' is not recognized as the name of a cmdlet, function, script file, or operable program. My guess was it has to do with scope. But making variable global didn't help. Adding -args $commandBlock like that: -ArgumentList ('-command `$Global:commandBlock -args "

What confuses me is decoding of HTTP header values . Example Header: Some-Header: "quoted string?"; *utf-8'en'Weirdness Can header value's be quoted? What about the encoding of a " itself? is ' a valid quote character? What's the significance of a semi-colon ( ; )? Could the value parser for a HTTP header be considered a MIME parser? I am making a transparent proxy that needs to transparently handle and modify many in-the-wild header fields. That's why I need so much detail on the format. Can header values be quoted? If you mean does the RFC 5987 parameter production apply to the main part of

CREATE OR REPLACE FUNCTION msgfailerror() RETURNS trigger AS ' BEGIN IF NEW.noces< new.first_column THEN RAISE EXCEPTION 'cannot have a negative salary'; END IF; return new; END' LANGUAGE plpgsql Trigger create trigger msgfail before insert on first for each row execute procedure msgfailerror() Giving error: syntax error at or near "cannot" LINE 5: RAISE EXCEPTION 'cannot have a negative ... I have almost one validation for each field of row. I want trigger to check all validations while insertion is being done and, raise error log afterwards once for all. Should I use raise exception on raise

I'm using code similar to the following in a Makefile: empty:= space:= $(empty) $(empty) path_escape = $(subst $(space),\$(space),$(1)) TOP=$(call path_escape,$(abspath .)) TARGET=$(TOP)/foo $(info TOP='$(TOP)') $(info TARGET='$(TARGET)') all: $(TARGET) $(TARGET): touch '$(notdir $@)' .PHONY: $(TARGET) If I use this in a directory with no spaces, say space-test , it works fine: $ make TOP='/tmp/space-test' TARGET='/tmp/space-test/foo' touch 'foo' However, if I use it in a directory with spaces, say space test , then $(notdir) does the wrong thing: TOP='/tmp/space\ test' TARGET='/tmp/space\