Dmitry Ledentsov

or [sqlpp11](https://github.com/rbock/sqlpp11-connector-sqlite3)

If it adds green tests, sure, you're welcome to open a PR. I think @paulftw won't mind

There are currently no resources to add further features (@paulftw, correct?). You might want to want to look at the non-lite alternatives, such as [sqlpp11](https://github.com/rbock/sqlpp11)

I don't think this feature belongs into anything with a name `*lite`

I'd go for the documentation of big frameworks and [other links](http://en.wikipedia.org/wiki/Schema_migration)

In my view, it would make sense if it's automatic and possibly a pre-commit hook. I've been thinking about using [Astyle](http://astyle.sourceforge.net/) or better [ClangFormat](http://clang.llvm.org/docs/ClangFormat.html), as it is based on a...

hm, maybe using the SRP and creating another object for that should be a cleaner way to solve the problem? Do you need the back-reference persistent? If not, you might...

P.S. with SRP I meant the [Single Responsibility Principle](http://www.objectmentor.com/resources/articles/srp.pdf), sorry for the ambiguity :)

@Oipo: > No support for back-reference. > As for the back-reference, I don't know what you mean with persistence? What I mean by persistence is the presence of that back-reference...

Thank you for your answer too, @Oipo. If I understand you correctly now, you'd like to see an abstraction for queries, such as joins in hiberlite.