?
avatar julienV
julienV
20 Nov 2018

Steps to reproduce the issue

In our component, we use a foreign key with constraint on checked_out column to the #_users table, to that we can use ON UPDATE/DELETE feature. To make this work, the default value must be null, and not 0, as there is no user with id 0.
It works fine while doing checkins internally to our component, but we get an error when use Joomla! global checkin feature on our tables, as it tries to set the value back to 0 instead of null.
The solution for this is to use DEFAULT keyword instead of 0 in the query.

Expected result

Checkin should reset checked_out value to the table column default

Actual result

it tries to reset the value to 0

System information (as much as possible)

joomla 3.9.0

Additional comments

avatar julienV julienV - open - 20 Nov 2018
avatar joomla-cms-bot joomla-cms-bot - labeled - 20 Nov 2018
avatar joomla-cms-bot joomla-cms-bot - change - 20 Nov 2018
Closed_Date 2018-11-20 16:11:22 2018-11-20 16:11:23
Closed_By Quy joomla-cms-bot
avatar joomla-cms-bot joomla-cms-bot - close - 20 Nov 2018
avatar Quy Quy - change - 20 Nov 2018
Status New Closed
Closed_Date 0000-00-00 00:00:00 2018-11-20 16:11:22
Closed_By Quy
avatar joomla-cms-bot
joomla-cms-bot - comment - 20 Nov 2018

Set to "closed" on behalf of @Quy by The JTracker Application at issues.joomla.org/joomla-cms/23121

avatar Quy
Quy - comment - 20 Nov 2018

See PR #23122


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23121.

avatar Quy
Quy - comment - 20 Nov 2018

See PR #23122


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23121.

Add a Comment

Login with GitHub to post a comment