# Spatial, Pluggable SQLite

DevFeed: [Spatial, Pluggable SQLite](<https://devfeed.tech/articles/spatial-pluggable-sqlite-19524.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/spatial-pluggable-sqlite/>)

Author: Shai Almog

Published: 2018-05-07T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Geographic Information System](<https://devfeed.tech/topics/gis.md>), [Databases](<https://devfeed.tech/topics/databases.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [gis](<https://devfeed.tech/tags/gis.md>), [ios](<https://devfeed.tech/tags/ios.md>), [security](<https://devfeed.tech/tags/security.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

## AI overview

The article describes a pluggable SQLite solution for Codename One applications that adds spatial query support for GIS use cases on Android and iOS. It also discusses encryption as a potential extension because the native SQL databases are not encrypted by default.

## Source excerpt

One of our enterprise accounts is working on a complex GIS application that needs fine grained control over mapping. In this case features such as native maps aren't useful. For some GIS applications the old MapComponent is more useful as it allows working with domain specific data. One of the features he needed was spatial support in the builtin SQL database. When we initially implemented sqlite support we just delegated all the SQL calls to the OS native equivalents and called it a day. This works well for 98% of the cases but there are two big use cases that are missing by default in Android & iOS: Spatial queries & Security.