Hey all, I think the best course of action here is to hold off until after 2.6 so we can review this thing as a whole solution rather then rushing it in last minute and then moving the target later.
IMO we could in the future use sqlite in memory datastore for the memory provider which gives us a lot more options and range. Changing the format of the project file to something that isn't xml is a interesting idea however it's not something that should be rushed into without consideration so I think that is a very different topic. - Nathan On Thu, Sep 25, 2014 at 5:19 PM, Matthias Kuhn <[email protected]> wrote: > Hi, > > Please excuse my ignorance, but > > Why would you want a memory (as in RAM) layer when you want permanent data? > > For portability reasons? > That's fine, but then we should offer a possibility to support portability > support for a real geo-format (with spatial index and all the goodies). To > stuff it into the project file there can be support from a plugin, but I > would not vote for adding this to core. > > To me it seems that the current demand for this comes mainly from wrong > expectations created by the name (and people subsequently loosing data). > And we can fix the name. > For the portability issue, I'd rather go the longer way but get it right. > > Regards > Matthias > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
