You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't been able to track down why, but over the past couple months we've seen instances where our timestamp columns aren't DateTime objects, but instead are strings. The occurrence so far seems to show up in random places.
The text was updated successfully, but these errors were encountered:
I encountered a similar problem while updating the library. Suddenly, my code began to throw an error that the date field is a string and not a DateTime object.
I remembered that the previous version was a bit fixed for me to work correctly with PostgreSql.
After transferring this fix, everything works correctly.
Perhaps the date fields remain strings due to some kind of hidden error.
My case is that the PostgreSQl adapter does not read the table structure that is outside the public schema. I fix the Table.php:
private function get_meta_data()
{
// as more adapters are added probably want to do this a better way
// than using instanceof but gud enuff for now
$quote_name = !($this->conn instanceof PgsqlAdapter);
I haven't been able to track down why, but over the past couple months we've seen instances where our timestamp columns aren't DateTime objects, but instead are strings. The occurrence so far seems to show up in random places.
The text was updated successfully, but these errors were encountered: