Re: Decoupling the ORM

As far as I'm concerned, anything we can do to simplify and decouple abstraction layers is a good thing and would be welcomed, with the usual caveats of backwards compatibility in public and pseudo-public APIs. models.query is a thin layer over models.sql.query. That's a good thing. Ideally,

Fellow Report - December 19, 2015

I spent about 2 days this week working on helping Adrienne launch the next round of fundraising (see "Authored" section for some details -- there were also a dozen or so other small pull requests that I didn’t bother to list). There might be some odds and ends to do next week, but I hope to

Re: [Question] MySQL Microseconds stripping

Aymeric is right. I do an insert with microseconds (since that's what django does right now) but mysql has the column defined as datetime(0), so it just strips the microsecond part, however, when doing the select, I'm expecting to get the value I have just inserted, but it doesn't work, since

Re: Decoupling the ORM

You've raise a very good point, one that has been on my mind the entire time I've been exploring this. Much of Django has been designed 'on the back of' the ORM, reliant on its limitations and without need to go beyond the scope of what it can provide, its very probable that over time this has

Re: Contribution towards the project

Welcome Yash, the "Advice for new contributors" area is probably a good first stop for dipping your toe in the water.. https://docs.djangoproject.com/en/1.9/internals/contributing/new-contributors/ On Wednesday, 16 December 2015 10:55:14 UTC, Yash Sharan wrote: > > Hello my name is yash

Re: [Question] MySQL Microseconds stripping

On Saturday 19 December 2015 11:23:17 Erik Cederstrand wrote: > > Den 19. dec. 2015 kl. 16.01 skrev Aymeric Augustin > > : > > > > To be fair, this has a lot to do with MySQL’s lax approach to storing > > data. There’s so many situations where it just throws

Re: [Question] MySQL Microseconds stripping

> Den 19. dec. 2015 kl. 16.01 skrev Aymeric Augustin > : > > To be fair, this has a lot to do with MySQL’s lax approach to storing data. > There’s so many situations where it just throws data away happily that one > can’t really expect to read back data

Re: [Question] MySQL Microseconds stripping

Hello, > On 19 déc. 2015, at 09:21, Erik Cederstrand wrote: > >> Den 19. dec. 2015 kl. 13.15 skrev Cristiano Coelho >> : >> >> The issue is that every datetime column created has no microseconds (since >> they were created with django 1.7,

Re: [Question] MySQL Microseconds stripping

> Den 19. dec. 2015 kl. 13.15 skrev Cristiano Coelho : > > Erik, > I'm using MySQL 5.6.x and indeed it has microseconds support, but that's not > the issue. > > The issue is that every datetime column created has no microseconds (since > they were created with django