Jan Aagaard Meier
Jan Aagaard Meier
@subjectix Actually we already have `sequelize.literal` which might be usefull here - we'd just need to implement support for that in the format method then
Why do you need it to be without timezone? You can set the timezone to something other than UTC if that's the problem Sequelize purposedly uses with timestamps to make...
Closing, no response
@gpedro Then I'll ask you the same question - why do you need this?
But no matter what, the time you are storing still represents a single point in time - to be able to identify that you need to store the timezone (or...
In case of a legacy system you don't need to worry about what `Sequelize.DATE` does, since the table is already created, right? In case you need to disable parsing of...
@arieljake Perhaps there is a bit of confusion about `.DATE` - `Sequelize.DATE` is represented as a `DATETIME` in the database - that is a date and time part, which inherently...
@arieljake Alright, I would think thats a bug, since representing a date as something with a time part (which javascript dates will always have) is wrong in my POW -...
https://github.com/sequelize/sequelize/issues/4858
@felixfbecker I see your point, but that would mean our API had to support (and test) three different ways of passing arguments. I'd rather keep it at the two we...