On 2019-09-23 1:22 p.m., Simon Slavin wrote:
Can I get an answer to my 'Subject' header ?
Is the parameter to the PRAGMA a string parameter ? If so, can the
documentation be changed to use apostrophes as delimiters ? Using double
quotes in the documentation seems really weird.
If, on the
On Monday, 23 September, 2019 14:09, Richard Hipp :
>In any event, you are correct that the behavior can now be disabled
>and should be for new applications. But we need to leave it turned on
>by default for legacy.
Nevertheless, the point is that even if you purportedly turn the behaviour
On 23 Sep 2019, at 9:09pm, Richard Hipp wrote:
> In any event, you are correct that the behavior can now be disabled
> and should be for new applications.
Can I get an answer to my 'Subject' header ?
Is the parameter to the PRAGMA a string parameter ? If so, can the
documentation be changed
On 9/23/19, Keith Medcalf wrote:
>
> due to a
> longstanding bug in SQLite3 you can use identifier quotes around strings
I don't think "bug" is quite the right word here, as the behavior was
deliberate. The use of double-quotes for strings was put in in a
(perhaps misguided) attempt to be more
te mailing list
>Subject: [sqlite] Why "UTF-8" and not 'UTF-8' ?
>
>The documentation for PRAGMA includes this command:
>
>PRAGMA encoding = "UTF-8";
>
>Why is it "UTF-8" and not 'UTF-8' ? Why is it double quotes rather than
>a normally-deli
On September 23, 2019 1:27:54 p.m. EDT, Simon Slavin
wrote:
>The documentation for PRAGMA includes this command:
>
>PRAGMA encoding = "UTF-8";
>
>Why is it "UTF-8" and not 'UTF-8' ? Why is it double quotes rather
>than a normally-delimited string ? Should either of these work ?
>
>PRAGMA
The documentation for PRAGMA includes this command:
PRAGMA encoding = "UTF-8";
Why is it "UTF-8" and not 'UTF-8' ? Why is it double quotes rather than a
normally-delimited string ? Should either of these work ?
PRAGMA encoding = UTF-8;PRAGMA encoding = 'UTF-8'
7 matches
Mail list logo