Simple Alternatives to Object-Relational Mapping for Android/SQLite
<p>I'm looking for simple techniques for getting OOP and RDBMS's to work well together. </p>

<p>I'd like to keep it as simple as possible, so no automatic code generation or ORM packages like <a href="http://ormlite.com/" rel="nofollow">ormlite</a>, but perhaps just POJOs, one for each DB table, with methods like fetchOne(int db_row_id) and fetchAll() that return a cursor.</p>

<p>The problem I keep running into is where to put methods that query two or more tables in a join, since the POJO representing a table has to then have pretty much as much knowledge about other tables as well. </p>

<p>The only alternative I can think of is to just have one class for handling the ORM that has probably around 50-100 methods, each doing its own query across one or many tables and returning a plain Cursor. </p>

<p>Yuk!!</p>
