see https://groups.google.com/forum/#!topic/spray-users/2UQnBJG5a80
In most cases there is no custom remove and delete feature required. But the
rare cases you have to write the features on your own and then have to register
them in the feature provider.
This should be supported by Spray either by
* pregenerate those feature classes by default (disadvantage: a lot more classes, advantage: easy entry point to add custom code)
* add syntax option in DSL to express that for certain mappings a remove and/or delete feature class should be pregenerated
Original issue reported on code.google.com by de.abg.r...@gmail.com on 1 Sep 2013 at 8:57
Original issue reported on code.google.com by
de.abg.r...@gmail.com
on 1 Sep 2013 at 8:57