On 7/26/16, Tim Gustafson wrote:
> This schema was created by the Webform module, which is a
> contributed module to the Drupal project. I will give your feedback
> to the developers of that module, but they're not using SQLite
> exclusively and there might be a reason why they
> If the column is INTEGER, the default value shouldn't be a string.
> This is especially true of the INTEGER PRIMARY KEY column.
I didn't make this schema, so I can take no credit (or blame) for its
design. This schema was created by the Webform module, which is a
contributed module to the
On 7/25/16, Richard Hipp wrote:
> On 7/25/16, Richard Hipp wrote:
>> If it is a bug, we'll fix it.
>
> It is a bug. The ticket is here:
> https://www.sqlite.org/src/tktview/a0bac8b3c3
The bug is now fixed on trunk. (See
On 7/25/16, Richard Hipp wrote:
> If it is a bug, we'll fix it.
It is a bug. The ticket is here: https://www.sqlite.org/src/tktview/a0bac8b3c3
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
On 7/25/16, Tim Gustafson wrote:
> I'm using SQLite as the back-end database for Drupal. One of the
> Drupal modules I use is called Webform, and Webform has a table that
> looks like this:
>
> CREATE TABLE "webform_submissions" (
> sid INTEGER NULL DEFAULT '',
If the column is
I'm using SQLite as the back-end database for Drupal. One of the
Drupal modules I use is called Webform, and Webform has a table that
looks like this:
CREATE TABLE "webform_submissions" (
sid INTEGER NULL DEFAULT '',
nid INTEGER NOT NULL DEFAULT '0',
uid INTEGER NOT NULL DEFAULT '0',
is_draft
6 matches
Mail list logo