Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

$row->copy doesn't work with Sybase and datetime fields #84

Closed
wants to merge 2 commits into from

Conversation

perlpunk
Copy link
Contributor

With the default datetime_setup, the date format delivered by Sybase
is not accepted for inserts.

Changing the format to ISO on connect (see comments in code), then the datetime parser
DBIx::Class::Storage::DBI::Sybase::ASE::DateTime::Format complains and
can simply be replaced by DateTime::Format::Sybase, which raises the question,
why we need the ASE datetime parser at all.

@ribasushi
Copy link
Collaborator

Ok, given the clusterfuck the best solution I could come up with is this workaround. I made it into a test so it is exercised going forward. Refer to the commit message for the gory details (though you already know most of them).

I do not have a more general solution in mind, short of "just make a new set of inflators/datetime_setup routines for the affected storages".

This is more or less the limit of what the current misdesigned system can do :/

@ribasushi ribasushi closed this Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants