What about null elements?
On Fri, Jul 13, 2018 at 12:11 PM Andrea Aime <[email protected]>
wrote:
> On Fri, Jul 13, 2018 at 8:41 PM, Jody Garnett <[email protected]>
> wrote:
>
>> No personal preference, just want to consider options, and wondering if
>> the design is working (or needs a workaround).
>>
>> I kind of thought we had a way to represent lists of content, indicate
>> the type of the list element, and then allow multiplicity to be zero to
>> any, nillable false.
>>
>
> The way I can think of would be to have the attribute with multiplicity >
> 1 in the schema, but then complex features would be needed
> (and hell gates would slam open, in GT we have no gentle path between
> simple and complex, there is simple, and then there is
> app-schema, nothing in between). Bridging that gap looks like to be a very
> large amount of work (e.g., for starters JDBCDataStore
> would have to become a JDBCDataAccess, with all the consequences of the
> case).
>
> With arrays there are no particular issues besides to-string (can be
> solved with a converter), the type is explicit enough that client
> code can determine what to put in the attributes for writes, and it's a
> 1-1 match for the database type (it's called an array in there).
> If it was read only I would be happy with a type-less list, but since
> writes are a requirement, the caller code needs enough info
> to determine what to put in the features to be written. Adding some info
> in the userdata map is possible, but it looks like a hack,
> compared to having direct type representation.
>
> Cheers
> Andrea
>
> ==
>
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
> http://www.geo-solutions.it http://twitter.com/geosolutions_it
> ------------------------------------------------------- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> GeoTools-Devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
