Welcome to floor Discussions!

[vitusortner]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[salvaterra]

Hi,

My name is Roddy thanks for the library - very helpful!

What do you think about adding this to the main readme.md ? I think people will appreciate going from 30 lines to 2 for each DAO.

abstract class GenericDao<T> {

  @insert
  Future<void> insertObj(T obj);

  @insert
  Future<void> insertObjs(List<T> objs);

  @update
  Future<void> updateObj(T obj);

  @update
  Future<void> updateObjs(List<T> objs);

  @delete
  Future<void> deleteObj(T obj);

  @delete
  Future<void> deleteObjs(List<T> objs);

  @Query('SELECT * FROM \$DB_TABLE WHERE id = :id')
  Future<T> findObjById(int id);

  @Query('SELECT * FROM \$DB_TABLE')
  Future<List<T>> findAllObjs();

  @Query('SELECT * FROM \$DB_TABLE')
  Stream<List<T>> findAllObjsAsStream();
}

@dao
abstract class CatDao extends GenericDao<Cat>{
  String DB_TABLE = 'Cat';
}

[vitusortner]

Hi @salvaterra! We have a section in the project's README that briefly mentions the capabilities of using abstract classes as base DAOs. If you feel like we could improve that section, feel free to open a pull request.

[TalebRafiepour]

How to write migrations when I increase the database version?
Is there any example? How can I reach that?
Thanks for answering me
@vitusortner

[dkaera]

Hi @TalebRafiepour
To run migration you need to increase the database version and add migration realization (from [oldVersion] to [newVersion] version). Here is an example https://github.com/vitusortner/floor/blob/7888578cda7e8d1982ff23d99e03334256768cd7/floor/test/adapter/migration_adapter_test.dart

[vitusortner]

You can find another example here https://vitusortner.github.io/floor/migrations/

[TalebRafiepour]

Thank you for your good support🌹🙏🙏🙏

[purplegamba]

Could someone please give me an example of how to use the 'unique' attribute in an entity? It's mentioned only very briefly in the documentation.

[purplegamba]

Never mind, I think I figured it out. Hopefully this is right:

@entity(tableName: 'person', indices: [Index(value: ['custom_name'], unique: true)])
class Person {
@PrimaryKey
final int id;

@ColumnInfo(name: 'custom_name', nullable: false)
final String name;

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

[ErliSoares]

First of all thank you very much for the library you are congratulating, I am very in doubt which library to use moor or floor, but I decided not to use any of them for now and use my custom one for now.

I just wanted to give feedback because I decided not to use this library for the time being.

• Not in production
• Use sqflite not sqlite3
• Moor library is having more coding frequency
• We do not have support for WEB, I even managed to use sqflite on the WEB, but there is no way to use an existing database for example

[vitusortner]

Thanks for your feedback. We're continuously improving the library.

Floor's first stable release is just around the corner. Once our dependencies have migrated to null-safe Dart, we're good to go.

[xocechka]

I'm having trouble with Foreign Key action's
I started with the basic example Person - Dog. I cant delete a Person who has a Dog associated. Sorry for the English.

[vitusortner]

Can you paste a code snippet to find out where the problem lies?

[Tedesc0]

First of all, thanks for the framework. I'm using it in a couple of projects an it is very helpful. I'd like to ask you to make the floor accept @required in the parameters for the DAO methods. I fought an error for a long time now and I think if the parameters were @required the problem haven't occurred. Thanks in advance and sorry for the english.

[vitusortner]

Yeah, expect behaving differently than expected sounds likely to me here too. @Tedesc0 what do you need the async block in async for?

[Tedesc0]

@vitusortner ,I create unit tests for all database operations defined in the Persistence, Services and Repository layers of my applications and the operations can reach hundreds. Doing all tests without expect statement is very laborious and takes a lot of time. As database operations are asynchronous all methods in all classes of those layers are also asynchronous. Only to see if the method ended without throwing an error it is necessary to write a try-catch for each of them and this takes time. I expect to have answered your question. Thanks a lot to reply to my post.

[mqus]

If you just want to check if operations run through without throwing an error I think you don't need expect or try at all, since the testing framework should already catch all errors and fail the test if an error occurs. As stackoverflow says the returnsNormally Matcher is only for nicer error messages.

PS: see also https://api.flutter.dev/flutter/test_api/throwsA.html for Futures. returnsNormally does not have the same documentation but I expect similar behaviour.

[mqus]

you probably want to use expectLater:

[...]
await expectLater(() async {
        user = await persistenceManager.usersPersistence.readById(id: UserId.from(id: 'USER-------0'));
      }, returnsNormally);
[...]

I haven't tried it out but it seems to match your expectations

[Tedesc0]

you probably want to use expectLater:

[...]
await expectLater(() async {
        user = await persistenceManager.usersPersistence.readById(id: UserId.from(id: 'USER-------0'));
      }, returnsNormally);
[...]

I haven't tried it out but it seems to match your expectations

@mqus i already tried expectLater() and it also shows the same problem. The strangest thing in this situation is that expect () works OK for the INSERT of rows in the database, but does not work when SELECTing these same rows. As we used to say in Portuguese, "I am more lost than a blind man in a shooting". Thanks a lot for your interest in this problem.

[fillsinger]

Hi @vitusortner

is it possible to model a many-to-many relationship in an entity as in Hibernate for example?
If not, how is it possible to handle many to many relationships?
e.g.

class Emplyoee {
  final int id;
  final String name;
  final List<Project> listofProjects;
}

[vitusortner]

Hi! Floor doesn't provide direct mapping for m-n relationships. You'll need to manually create an association table to map the relationships. A ticket for the requested functionality can be found here #47.