Closed springmeyer closed 13 years ago
In fact, I can create any filename I like the the layer UI, the mml is updated, and the project rendering does not change:
$ cat ../intro.mml | grep "file"
"file": "/Users/dane/Desktop/demo/project/thisdoesnotexist.sqlite",
okay, I see now that you have to update the layer #id to get the symlinks to update. -1 on this behavior.
I will have to look at this more closely in millstone... I know that there are some limitations to what we can do here.
For example, it's not actually possible to efficiently know when a symlink is out of date for URL zip resources because you would have to download and unzip the resource every time, eliminating the usefulness of localization/caching.
For absolute files on the filesystem, however, it may be reasonable to check symlinks every time to make sure they point at the right place.
Yes, local filesystem paths are the issue here which I think need fixing. Having to change the #id requires changing both your layer and your style and litters your project folder with dead symlinks.
Should be fixed with https://github.com/mapbox/millstone/commit/0b21f2f76a244eb4de08e876314d997604c867b0
I tested with two local sqlite datasources as well as running the tests but would love confirmation from someone that the fix above works.
tested, this is fixed! thank you!
Awesome, it works!
On OSX 10.6.8, tilemill master @ 2b2794d8.
* Datasource
input line to point to a different sqlite fileAt this point rendering still uses the old layer. The reason for this is visible by viewing the Mapnik XML at
The XML shows:
Which indicates a symlink is pointed to for accessing the layer, and that symlink is the same name (did not change), and that symlink points to the same original filename.
Curiously the mml file is pointing to the right sqlite file "countries_dane.sqlite" vs "countries.sqlite":
And here are the details on those files: