Dr. W. Shawn Wilkerson

It is functionally similar to IN without the casting IN performs. If memory serves, FIND_IN_SET is also much heavier at the query level, doesn't use indexes, and easily breaks if...

@Kossin7 Currently, we use xPDO::toJSON and xPDO::fromJSON to save the JSON to a text field. I understand MODX3 has a minimum MySQL version of 2.6, I do not know if...

To get around this I have used clone in the past. That way the first object can die and leave the cloned object unaffected.

I do not believe xPDO would be the issue here. xPDO should not be ignoring anything to do with the case. `cAsE !== casE !== CASE !== Case` Per the...

You should never edit the core files as they may be overwritten during updates.

Was the databases defined as _ci to handle the case issues in the table definitions?

> > > **wshawn** please explain what you mean? ci is for case-insensitive sorting and comparison. It tells the database to ignore case. As this issue is a bit old,...

> > > If I'm not mistaken a workaround that doesn't require to modify the source: > This requires an instance of xPDO > > ``` > $xpdo->getDriver()->$_currentTimestamps[] = 'current_timestamp()';...

I concur. Please fix this. I have mentioned this issue several times over the years. I have to manually go into the database tables after xPDO creates them and alter...

What @Mark-H said. That was my original point of the post. It also, seems to grab only one charset per table. My only workaround has been to manually change the...