On 11/11/2017 8:55 PM, Balaji Ramanathan wrote:
3.When there is a mathematical expression after the string, I get a 0.
My string is nowhere to be seen in the output
SQLite> select '- '||cast(-1.5 as integer)*-1
0
|| has the highest precedence. Your expression is interpreted as ( '-
I am not sure what exactly is going on here. When an expression starts
with a string and I try to append the results of a mathematical operation
to it, sometimes it works, sometimes, it doesn't, and I can't find the
pattern behind what works and what doesn't.
1.Simple mathematical expression
Thanks all for the info. I'm still doing thought wrestling on the
path I want to take.
On one hand, its brain dead simple for me to go the tokenizer route
and have my application dynamically generate the SQL string, I just
don't like that kind of code style as there are many faults with it,
Hello,
I don't know know if this is an openBSD issue or something with sqlite3
- posting here for guidance.
I'd like to make a loadable module for csv, but when attempting to
generate the so file, I see this:
$ gcc -g -fPIC -shared csv.c -o csv.o
csv.c:42:24: error: sqlite3ext.h: No such
On 2017/11/11 7:23 PM, Bart Smissaert wrote:
Yes, that this is mainly for SQLite and thanks for explaining and that is
what I thought.
I think square brackets are better than double quotes as it looks better
and parsing SQL
gets easier as the opening and closing character are not the same. But
On 11/11/17, R Smith wrote:
>
> Further to this, an Identifier can remain unquoted (plain text), except:
>
> - when it is the same as an SQLite Keyword.
Correct.
Unfortunately, we do occasionally add new keywords. The most recent
example is version 3.8.3 (2014-02-03)
Yes, that this is mainly for SQLite and thanks for explaining and that is
what I thought.
I think square brackets are better than double quotes as it looks better
and parsing SQL
gets easier as the opening and closing character are not the same. But then
for compatibility
with other DB's double
On 2017/11/11 6:43 PM, Simon Slavin wrote:
On 11 Nov 2017, at 4:40pm, Kees Nuyt wrote:
It conforms to the SQL standard, you can use the Postgresql docs
as a reference.
https://www.postgresql.org/docs/7.1/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS
"the SQL standard
On 2017/11/11 1:04 PM, Bart Smissaert wrote:
What are the exact rules for valid identifier names (tables, columns and
indexes)?
This is both for names enclosed in square brackets ([]) or double quotes
(") and also for names
that are not enclosed within square brackets or double quotes.
The
On 11 Nov 2017, at 4:40pm, Kees Nuyt wrote:
> It conforms to the SQL standard, you can use the Postgresql docs
> as a reference.
>
> https://www.postgresql.org/docs/7.1/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS
"the SQL standard will not define a key word that contains
On Sat, 11 Nov 2017 11:04:37 +, Bart Smissaert
wrote:
> What are the exact rules for valid identifier names (tables, columns and
> indexes)?
> This is both for names enclosed in square brackets ([]) or double quotes
> (") and also for names
> that are not enclosed
On 11 Nov 2017, at 11:04am, Bart Smissaert wrote:
> What are the exact rules for valid identifier names (tables, columns and
> indexes)?
There is no documentation for this. Which means that even if you find that,
say, macrons are allowed in this version, they might
What are the exact rules for valid identifier names (tables, columns and
indexes)?
This is both for names enclosed in square brackets ([]) or double quotes
(") and also for names
that are not enclosed within square brackets or double quotes.
Had a good look for this, but couldn't find a clear
13 matches
Mail list logo