See the project's website for the full documentation.

Floor provides a neat SQLite abstraction for your Flutter applications inspired by the Room persistence library. It comes with automatic mapping between in-memory objects and database rows while still offering full control of the database with the use of SQL. As a consequence, it's necessary to have an understanding of SQL and SQLite in order to harvest Floor's full potential.

• null-safe
• typesafe
• reactive
• lightweight
• SQL centric
• no hidden magic
• no hidden costs
• iOS, Android, Linux, macOS, Windows, web

⚠️ The library is open to contributions! Refer to GitHub Discussions for questions, ideas, and discussions.

Migrating from Floor

The community packages intentionally keep the familiar Floor annotation and generated API surface. In normal application code, the primary migration is the dependency/import swap:

// Before
import 'package:floor/floor.dart';

// After
import 'package:floor_community/floor.dart';

Annotations such as @Entity, @entity, @PrimaryKey, @primaryKey, @dao, @Query, @insert, @update, @delete, @transaction, @Database, @DatabaseView, and @TypeConverters keep their Floor-compatible names. Generated database entry points also keep the $Floor<DatabaseName> convention.

When migrating an installed application, keep the same database filename, schema version, table/column names, and migration chain. Regenerate the .g.dart files; do not delete or recreate the database merely because the package dependency changed. See docs/MIGRATION.md for the compatibility checklist.

Getting Started

1. Setup Dependencies

Add the runtime dependency floor_community as well as the generator floor_generator_community to your pubspec.yaml. The third dependency is build_runner, which should be included as a dev dependency just like the generator. Use the compatibility range shown below instead of forcing the newest exact release; Flutter SDK packages can pin transitive dependencies used by the Analyzer toolchain.

• floor_community holds all the code you are going to use in your application.
• floor_generator_community includes the code for generating the database classes.
• build_runner enables a concrete way of generating source code files.

dependencies:
  flutter:
    sdk: flutter
  floor_community: ^1.1.0

dev_dependencies:
  floor_generator_community: ^1.1.0
  build_runner: ">=2.15.0 <3.0.0"

2. Create an Entity

It will represent a database table as well as the scaffold of your business object. @entity marks the class as a persistent class. It's required to add a primary key to your table. You can do so by adding the @primaryKey annotation to an int property. There is no restriction on where you put the file containing the entity.

// entity/person.dart

import 'package:floor_community/floor.dart';

@entity
class Person {
  @primaryKey
  final int id;

  final String name;

  Person(this.id, this.name);
}

3. Create a DAO (Data Access Object)

This component is responsible for managing access to the underlying SQLite database. The abstract class contains the method signatures for querying the database which have to return a Future or Stream.

• You can define queries by adding the @Query annotation to a method. The SQL statement has to get added in parenthesis. The method must return a Future or Stream of the Entity you're querying for.
• @insert marks a method as an insertion method.

// dao/person_dao.dart

import 'package:floor_community/floor.dart';

@dao
abstract class PersonDao {
  @Query('SELECT * FROM Person')
  Future<List<Person>> findAllPeople();

  @Query('SELECT name FROM Person')
  Stream<List<String>> findAllPeopleName();

  @Query('SELECT * FROM Person WHERE id = :id')
  Stream<Person?> findPersonById(int id);

  @insert
  Future<void> insertPerson(Person person);
}

4. Create the Database

It has to be an abstract class which extends FloorDatabase. Furthermore, it's required to add @Database() to the signature of the class. Make sure to add the created entity to the entities attribute of the @Database annotation. In order to make the generated code work, it's required to also add the listed imports.

Make sure to add part 'database.g.dart'; beneath the imports of this file. It's important to note that 'database' has to get exchanged with the filename of the database definition. In this case, the file is named database.dart.

// database.dart

// required package imports
import 'dart:async';
import 'package:floor_community/floor.dart';
import 'package:sqflite/sqflite.dart' as sqflite;

import 'dao/person_dao.dart';
import 'entity/person.dart';

part 'database.g.dart'; // the generated code will be there

@Database(version: 1, entities: [Person])
abstract class AppDatabase extends FloorDatabase {
  PersonDao get personDao;
}

5. Run the Code Generator

Run the generator with dart run build_runner build. To automatically regenerate when files change, use dart run build_runner watch.

6. Use the Generated Code

For obtaining an instance of the database, use the generated $FloorAppDatabase class, which allows access to a database builder. The name is being composed by $Floor and the database class name. The string passed to databaseBuilder() will be the database file name. For initializing the database, call build() and make sure to await the result.

In order to retrieve the PersonDao instance, invoking the persoDao getter on the database instance is enough. Its functions can be used as shown in the following snippet.

final database = await $FloorAppDatabase.databaseBuilder('app_database.db').build();

final personDao = database.personDao;
final person = Person(1, 'Frank');

await personDao.insertPerson(person);
final result = await personDao.findPersonById(1);

For further examples take a look at the example and test directories.

Naming

The library's name derives from the following. Floor as the bottom layer of a Room which points to the analogy of the database layer being the bottom and foundation layer of most applications. Where fl also gives a pointer that the library is used in the Flutter context.

Bugs, Ideas, and Feedback

For bugs please use GitHub Issues. For questions, ideas, and discussions use GitHub Discussions.

Announcement

Copyright 2023 The Floor Project Authors

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.