Open Source Mobile Operating Systems Object-Relational Mapping (ORM) Software

DBFlow is fast, efficient, and feature-rich Kotlin database library built on SQLite for Android. DBFlow utilizes annotation processing to generate SQLite boilerplate for you and provides a powerful SQLite query language that makes using SQLite a joy. DBFlow is built from a collection of some of the best features of many database libraries. Don't let an ORM or library get in your way, let the code you write in your applications be the best as possible. Built using the language, the library is super-concise, null-safe and efficient. Generates the necessary code that you don't need to write. Contains the main annotations and misc classes that are shared across all of DBFlow. The main library artifact used in conjunction with the previous two artifacts. Adds coroutine support for queries. Enable applications to be reactive by listening to DB changes and ensuring your subscribers are up-to-date.

Within this project, an orm framework for android is developed to store data by using an SQLite Database.

CCM is a solution for the data management layer in the combination of Sql Server with a C # application. In whole this is a strongly typed entity mapper projecting the application's business logics onto database tables using T-SQL stored procedures. CCM allows you to implement fairly complex data structures in your application, without bothering about difficult and tedious questions of data acquisition and conversion issue, allowing you to pay more attention to the develop of business logic and UI. There no need to worry about migrations, context, etc. At the same time, ORM completely relieves the developer from direct communicating with ADO - datasets, tables, rows, and other data aceess component, to track connections, commands or operate with adapters because ORM works at a higher level of data abstraction. At the same time you will be completely protected from memory leaks and free to create complexity application logic at the primary data level.

This is android library to simplify Android SQlite Database It become very tedious to write large Android SQLite Open helper for simple database usage. So I developed this library to create android databases very easily using straight forward functions. Github Project https://github.com/adityakamble49/DBXDroid Refer DBXDroidDemo for Full Demo https://github.com/adityakamble49/DBXDroidDemo

KittyORM is an Object-Relational Mapping library designed for use with Android and SQLite. It implements Data Mapper pattern design and its main purpose is to simplify interaction with SQLite database in Android applications. Written in Java 7 it supports devices from API level 9 Android. Main features we want to achieve with KittyORM are: * simple and clear API; * high flexibility of working with model POJO files via database mappers that grants you an ability to focus on your business processes not on working with raw SQL queries; * full support of all features to create your SQLite schema via built-in annotations; * flexible way to manage all things you may want to change or implement; KittyORM project contains ORM library itself, demo and tutorial application available at Play Market and documentation located at https://akaish.github.io/KittyORMPages/ Current version: [0.1.2]

This package provides Android-specific functionality. Users that are connecting to SQL databases via JDBC connections should download the ormlite-jdbc package instead of this Android one. Object Relational Mapping Lite (ORM Lite) provides some simple, lightweight functionality for persisting Java objects to SQL databases while avoiding the complexity and overhead of more standard ORM packages.

ObjectMapper is a framework written in Swift that makes it easy for you to convert your model objects (classes and structs) to and from JSON. Once your class implements Mappable, ObjectMapper allows you to easily convert to and from JSON. Use functions to validate JSON prior to object serialization provide an existing cached object to be used for mapping, return an object of another type (which also conforms to BaseMappable) to be used for mapping. For instance, you may inspect the JSON to infer the type of object that should be used for mapping. ObjectMapper supports dot notation within keys for easy mapping of nested objects. ObjectMapper also supports custom transforms that convert values during the mapping process. To use a transform, simply create a tuple with map["field_name"] and the transform of your choice on the right side of the <- operator.

This project moved to GitHub. Please go to https://github.com/productionReady/eleflex/ to get the latest source code.

Android ORM for your SQLite database. For new apps we recommend ObjectBox, a new object-oriented database that is much faster than SQLite and easier to use. For existing apps based on greenDAO we offer DaoCompat for an easy switch (see also the announcement). greenDAO is an open source Android ORM making development for SQLite databases fun again. It relieves developers from dealing with low-level database requirements while saving development time. SQLite is an awesome embedded relational database. Still, writing SQL and parsing query results are quite tedious and time-consuming tasks. greenDAO frees you from these by mapping Java objects to database tables (called ORM, “object/relational mapping”). This way you can store, update, delete, and query for Java objects using a simple object oriented API. We want to provide the fastest Android ORM.

xUtils includes orm, http(s), image, view annotations, but it is still very lightweight (251K), and has powerful features and is easy to expand. Efficient and stable orm tool, which makes it more convenient to support cookies and caching when the http interface is implemented. Based on UrlConnection, the bottom layer will be implemented by okHttp after Android4.4. The request protocol supports 11 predicates: GET, POST, PUT, PATCH, HEAD, MOVE, COPY, DELETE, OPTIONS, TRACE, CONNECT. Supports uploading of very large files (over 2G). Support breakpoint download (if the server supports the Range parameter, the client automatically handles the breakpoint download). Support cookies (implements domain, path, expiry and other features). Support caching (implement Cache-Control, Last-Modified, ETag and other features, use expiration time + LRU dual mechanism to clean up when the cache content is too much).