SQLite doesn't save filter choice #356

Closed
webkluns opened this Issue May 11, 2011 · 1 comment

Projects

None yet

2 participants

@webkluns
Contributor

Steps to reproduce when using SQLite:

  1. Create a new page, by default it has no filter.
  2. Use Textile or Markdown on some content and save the page
  3. Try to set that page to use no filter and save it.

Notice that it didn't seem to save the no filter state and instead returned to the last filter used.
Switching between Textile and Markdown and saving is not a problem, saving with no filter is.

Member
dajare commented May 12, 2011

Duplicates issue 305.

@dajare dajare closed this May 12, 2011
@kevinpsiu kevinpsiu added a commit to kevinpsiu/wolfcms that referenced this issue Jun 18, 2012
@kevinpsiu kevinpsiu Fix for issues #305, #324, #355 related to SQLite
The three bugs (and others duplicated such as #356) were all related to
one single problem in the `Framework`, namely that empty values were
not being handled properly for SQLite. Since SQLite does not support
DEFAULT keyword, an empty string must be explicitly passed in order to
properly update the record. The issues mentioned all involved
attempting to insert empty values in the database which was not caught
by the `if` statement on line 590.
4350d0e
@kevinpsiu kevinpsiu added a commit to kevinpsiu/wolfcms that referenced this issue Jun 18, 2012
@kevinpsiu kevinpsiu Fix issues #305, #324, #355
The three bugs (and others duplicated such as #356) were all related to
one single problem in the Framework, namely that empty values were not
being handled properly for SQLite. Since SQLite does not support the
DEFAULT keyword, an empty string must be explicitly passed in order to
properly update the record. The issues mentioned all involved
attempting to insert empty values in the database which was not caught
by the if statement on line 595.
0418411
@marekmurawski marekmurawski pushed a commit to marekmurawski/wolfcms that referenced this issue Feb 15, 2013
@kevinpsiu kevinpsiu Fix issues #305, #324, #355
The three bugs (and others duplicated such as #356) were all related to
one single problem in the Framework, namely that empty values were not
being handled properly for SQLite. Since SQLite does not support the
DEFAULT keyword, an empty string must be explicitly passed in order to
properly update the record. The issues mentioned all involved
attempting to insert empty values in the database which was not caught
by the if statement on line 595.
a338b76
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment