Re: Help needed with Oracle GIS backend

As we approach 1.9 alpha in about a month and half, no one has stepped up to offer help fix the Oracle GIS backend. Should we use another platform like the djangoproject.com blog to make a final plea for help? On Monday, March 30, 2015 at 9:34:10 AM UTC-4, Jani Tiainen wrote: > > On Thu, 26 Mar

Re: Help needed with Oracle GIS backend

On Thu, 26 Mar 2015 22:29:00 +0200 Shai Berger wrote: > Hi Jani. > > On Wednesday 25 March 2015 09:58:00 Jani Tiainen wrote: > > > > We're still running Oracle and GIS. Though we do have built custom > > backend based on Django GIS backend - mainly to have support for > >

Re: Help needed with Oracle GIS backend

Hi Jani. On Wednesday 25 March 2015 09:58:00 Jani Tiainen wrote: > > We're still running Oracle and GIS. Though we do have built custom > backend based on Django GIS backend - mainly to have support for > Oracle XE, 3D functionality and in general to make it faster. > > It's currently closed

Re: Help needed with Oracle GIS backend

Before the fellowship started, I worked a bit on Oracle GIS to fix it up and get its tests passing, but I'm unsure if I should continue to try to do so as part of my duties in the absence of anyone else stepping up. Clearly if no one uses this backend, it's wasted effort. Should we try

Re: Help needed with Oracle GIS backend

Hi, We're still running Oracle and GIS. Though we do have built custom backend based on Django GIS backend - mainly to have support for Oracle XE, 3D functionality and in general to make it faster. It's currently closed source but we're working on to open source it in hope that it could interest

Re: Help needed with Oracle GIS backend

I also advertised this on the geodjango mailing list with the following message : Do we have any users of the Oracle GIS backend that have interest and ability to help maintain it? Claude has worked on several issues for 1.9

Help needed with Oracle GIS backend

Hi, In ticket #24214, I built a patch to replace all geo-specific Manager methods by class-based ORM functions. This will allow us to get rid of convoluted query code in the GeoDjango ORM. It will also be far much easier to add support for specific database functions. The code is already in