Re: Oracle backend and passing data as is.

2016-05-18 Thread Aymeric Augustin
Yes, we have a lot of code in this area. It isn’t particularly complex, but it isn’t always easy to tell what problem a particular line of code solves either. I’m afraid “educated guesses” are your best option at this point. Conditionally skipping some type conversions on sufficiently modern cx_

Re: Oracle backend and passing data as is.

2016-05-18 Thread Jani Tiainen
Hm. I was able to figure out what it was and do have hack around that. OracleParam class does certain checks, mainly it chekcs if param is date/time/timedelta or true/false. Otherwise it converts everything to string. And that's where backend thinks that WKTAdapter coming from Oracle GIS ba

Re: ***SPAM*** Re: Middleware+Transactions:

2016-05-18 Thread Florian Apolloner
Starting with Django 1.10 you can write a TransactionMiddleware again, and we will probably ship one again. On Tuesday, May 10, 2016 at 2:07:30 AM UTC+2, Kevin Tran wrote: > > Thomas, did you ever find a solution to your problem? I'm having similar > thoughts and am looking for an answer. > > O

Re: ***SPAM*** Re: Middleware+Transactions:

2016-05-18 Thread charettes
As MIDDLEWARE supports decorator-like objects you could simply add `django.db.transaction.atomic' to it and you'd get each request wrapped in a transaction. Note that this will only start a transaction on the `default` database, just like the old TransactionMiddleware use to do. Simon Le merc

Re: status of 1.10 release blockers

2016-05-18 Thread Tim Graham
A couple issues remain before the alpha release: Issue: Fixing some new-style SessionMiddleware to process the response even if the view raises an exception. Status: This is somewhat in design decision needed if anyone would like to take a look and offer feedback. I'll look at it more closely to

New CharField attribute to handle CharField(null=True, blank=True, unique=True) in model forms

2016-05-18 Thread Jon Dufresne
Hi, Occasionally I'll need to define a CharField on a model that is unique but also allow blank values. At the database level, this is easily handled by storing NULL for the blank values. (Storing the empty string multiple times will result in a DB unique constraint violation.) This use case has s

Organizing the built-in system check framework's hint messages

2016-05-18 Thread Quentin Fulsher
Hi all, Recently I was trying to fix a bug that required me to alter the hint message of the `fields.E306`[1] system check error[2]. The bug in question added a condition to a check which if failed caused the instantiation of a `django.core.checks.Error` object. In order to change the `Error`'