Hi,
We ran exactly same situation and we actually wrote did a slightly different
solution - we now do have (yet to be opensourced) a backend that actually reads
SDO_GEOMETRY directly and writes a string that resembles SDO_GEOMETRY and is
parsed to real SDO_GEOMETRY with small PL/SQL package
Hi Collin and Aymeric,
On 11/03/2014 03:26 PM, Aymeric Augustin wrote:
> Hi Collin,
>
> It’s exactly the right time to discuss APIs :-)
>
> After pondering your proposal, I'm still +0 on consistency with
> DATABASES and CACHES, but I'll make that change if other people agree
> with you. Does
Hi Collin,
It’s exactly the right time to discuss APIs :-)
After pondering your proposal, I'm still +0 on consistency with DATABASES and
CACHES, but I'll make that change if other people agree with you. Does anyone
else have an opinion on this?
Thanks,
--
Aymeric.
> On 3 nov. 2014, at
I don't see any problem having them coexist. After all it's just a
"call_command()" that I already implemented. I'd only need to remove the
deprecation warning.
On Monday, November 3, 2014 8:41:28 PM UTC+1, Tim Graham wrote:
>
> If we went with a separate command, would there be any problem
If we went with a separate command, would there be any problem having
--list on both migrate and showmigrations. I feel like deprecating it off
of migrate will cause more complaints about needless deprecations.
On Wednesday, October 29, 2014 9:28:51 PM UTC-4, Andrew Godwin wrote:
>
> This used
Hi Aymeric,
Great work!
I'm afraid that my review comments are lengthy. Feel free to suggest
that I provide them in some other format (issues and/or PRs on
https://github.com/aaugustin/mtefd ?) if that would be more useful.
* In the rationale section, it may be worth mentioning the specific
I had a look at the patch. As I mentioned on the ticket, "I am not really
happy with that patch which copies the
simple_server.WSGIRequestHandler.handle() method from Python's version in
order to override it. The copied version is not in sync with the latest
Python and I'd prefer not to be in
