On 28 Jun 2018, at 5:43am, Igor Tandetnik wrote:
> It's not mentioned here though:
> https://sqlite.org/syntax/column-constraint.html
The syntax diagrams in the SQLite documentation are ... what's the term ? ...
sufficient but not exhaustive. In other words you can use some forms which
viola
Great explanation. Thanks.
On Wed, Jun 27, 2018 at 7:43 PM Richard Hipp wrote:
> On 6/27/18, Igor Tandetnik wrote:
> > On 6/27/2018 9:14 PM, Richard Hipp wrote:
> >> On 6/27/18, Mark Wagner wrote:
> >>> Thanks for all the good background. FWIW this came up because someone
> >>> had
> >>> cre
On 6/27/2018 10:43 PM, Richard Hipp wrote:
On 6/27/18, Igor Tandetnik wrote:
On 6/27/2018 9:14 PM, Richard Hipp wrote:
On 6/27/18, Mark Wagner wrote:
Thanks for all the good background. FWIW this came up because someone
had
created a row with something like: (column_name non null). Needle
On 6/27/18, Igor Tandetnik wrote:
> On 6/27/2018 9:14 PM, Richard Hipp wrote:
>> On 6/27/18, Mark Wagner wrote:
>>> Thanks for all the good background. FWIW this came up because someone
>>> had
>>> created a row with something like: (column_name non null). Needless to
>>> say, this created a c
On 6/27/2018 9:14 PM, Richard Hipp wrote:
On 6/27/18, Mark Wagner wrote:
Thanks for all the good background. FWIW this came up because someone had
created a row with something like: (column_name non null). Needless to
say, this created a column without a "not null" constraint.
It should ha
Sorry, my typo (I had entered the corrected code). This:
create table t1(x text non null);
insert into t1(x) values(null);
select * from t1;
On Wed, Jun 27, 2018 at 6:14 PM Richard Hipp wrote:
> On 6/27/18, Mark Wagner wrote:
> > Thanks for all the good background. FWIW this came up beca
On 6/27/18, Mark Wagner wrote:
> Thanks for all the good background. FWIW this came up because someone had
> created a row with something like: (column_name non null). Needless to
> say, this created a column without a "not null" constraint.
It should have. I get an error when I type:
CREATE
On Wed, Jun 27, 2018, 7:47 PM Keith Medcalf wrote:
>
> If you give the parent column a proper affinity (ie, integer) do you get
> "happiness making" results?
>
> ---
> The fact that there's a Highway to Hell but only a Stairway to Heaven says
> a lot about anticipated traffic volume.
>
>
> >-
Thanks for all the good background. FWIW this came up because someone had
created a row with something like: (column_name non null). Needless to
say, this created a column without a "not null" constraint.
On Wed, Jun 27, 2018 at 5:02 PM Richard Hipp wrote:
> On 6/27/18, Mark Wagner wrote:
On 6/27/18, Mark Wagner wrote:
> I recently pointed out that sqlite doesn't enforce type names and
> constraints when creating tables but I was unable to explain/justify this
> behavior. I'm sure this has come up before and there's a clear answer but
> I didn't find it easily.
>
> For example thi
On 6/27/2018 6:56 PM, Mark Wagner wrote:
I recently pointed out that sqlite doesn't enforce type names and
constraints when creating tables but I was unable to explain/justify this
behavior.
https://sqlite.org/datatype3.html
SQLite attempts to be maximally compatible with a wide variety of da
If you give the parent column a proper affinity (ie, integer) do you get
"happiness making" results?
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>bo
In the current tip of trunk it pretends the unknown tokens are surrounded by
double-quotes. Until you interpose a non type keyword ... at which point the
parser stops "eating your junk as the type declaration" and resumes the grammar
..
sqlite> create table x(x happy days);
sqlite> pragma tab
On 27 Jun 2018, at 11:56pm, Mark Wagner wrote:
> I recently pointed out that sqlite doesn't enforce type names and
> constraints when creating tables but I was unable to explain/justify this
> behavior. I'm sure this has come up before and there's a clear answer but
> I didn't find it easily.
T
I recently pointed out that sqlite doesn't enforce type names and
constraints when creating tables but I was unable to explain/justify this
behavior. I'm sure this has come up before and there's a clear answer but
I didn't find it easily.
For example this is accepted without error: CREATE TABLE
I have a table with an additional index and a query:
"create table Transactions (Id integer primary key not null, Parent
references Transactions(id), Body varchar);"
"create index Parent_Index on Transactions (Parent);"
EXPLAIN QUERY PLAN insert or replace into Transactions (Id, Parent,
Body) va
16 matches
Mail list logo
