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

model saving can't handle datetime columns #4493

Open
eerhardt opened this issue Nov 21, 2019 · 0 comments
Assignees

Comments

@eerhardt
Copy link
Member

@eerhardt eerhardt commented Nov 21, 2019

@FranzBl commented on Wed Nov 20 2019

Sorry I couldn't answer earlier. To change column type of database, I had to change the program that generates it (in many places) and to setup a new database.
Indeed with data type real instead of float the program works incl. evaluating, training etc. With one exception: Trying to save the model to a zip file for later use on end fails. Reason: One table column is type datetime (in SQL). During generation of the data view this is converted into string, and training works. Saving the model attempts to change these column data back from string to datetime, so an exception is thrown.
Is this as should be? If model saving tries to reconstruct the original data types, so I think it should be able to parse a string as datetime.
In fact I could store the timestamps as simple strings in the database. But many database queries use datetime arithmetics, e. g. retrieving all data between two timestamps (SQL can do this very easy, while the date arithmetics on strings would be a little tricky).

Originally posted by @FranzBl in dotnet/machinelearning-samples#744 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.