One-to-many support.

[Queatz]

There are a few changes here.

• Bidirectional relationships are handled internally, so the user doesn't have to mark one an inverse anymore or pay attention to that (this was causing lots of problems with one-to-many.) This is done by temporarily caching just the prior Entities that could induce the circular reference. In order to support this, the Primary Key is the first field to be filled when an Entity is loaded.
• One-to-many support. This adds a List TypeMapping, however the only supported list is currently an Entity list.
• Simple order by in DESC.
• Close leaked cursor.

There are a few white-space removals, I apologize for that. My editor auto trims.

[ChristopheCVB]

Wow ! You made it ?!

I'll test it tomorrow !

[ChristopheCVB]

Can you provide a full example usage of this new feature ?

[Queatz]

@ChristopheCVB it's a simple implementation and not very smart, so I'd only use it for small projects. For small projects it should work great, though.

Basic usage is like this:

Person.java

class Person extends Entity {
    public String name;

    @Column(inverse = "person")
    public ArrayList<Hobby> hobbies;
}

Hobby.java

class Hobby extends Entity {
    public String type;
    public Person person;
}

And then you would just use it like normal:

Person person = Entity.query(Person).where(eql("name", "Christ")).execute();

for(Hobby hobby : person.hobbies)
    Log.d(TAG, "Hobby found: " + hobby.type);

Hope this helps!

[roscopeco]

This is now in master. Thanks again @Queatz and sorry it took so long!

[Queatz]

Awesome, good to have it. :)

[akinadude]

it seems to me this feature doesn't work or may be I do something wrong. Question and code snippets here http://stackoverflow.com/questions/24697824/ormdroid-one-to-many-relationship