Skip to content
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.

[ffi] Consider a loosely typed Android SDK #786

Open
ncalexan opened this issue Jul 16, 2018 · 0 comments
Open

[ffi] Consider a loosely typed Android SDK #786

ncalexan opened this issue Jul 16, 2018 · 0 comments
Labels
A-ffi A-sdk-android Android SDK related issues

Comments

@ncalexan
Copy link
Member

I was reading the Datomic documentation, and they emphasized that the Datomic API is built on the foundations the JVM provides rather than having, e.g., a ResultSet API. From https://docs.datomic.com/on-prem/architecture.html:

The ability to query and access data locally has a profound effect on the code in a Peer. Query results are directly accessible as simple data structures. There is no need to deal with the command and resultset abstractions common to most traditional database APIs, nor the object-relational mapping layers intended to hide them. A simple group of functions that encapsulates building and executing queries and transactions is sufficient.

Now, Datomic's position here is rather different from Mentat's, but there's something to be said for "just lists" and "just data". Maybe we could explore exposing lists-of-maps (ArrayList of HashMap) in the Android SDK and see how it feels?

@fluffyemily do you have strong feelings about this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-ffi A-sdk-android Android SDK related issues
Projects
None yet
Development

No branches or pull requests

1 participant