IgnitedRecord 1.0 pre-release

[eluser]obsesif[/eluser]
Cool datamapping library, i am really thankful, that someone took the initiative to start such an important layer.
As a novice database-user, it is a bit painful to me to understand the configuration alternatives.
I started first with models, then tried YAML and now preferring on-the-fly generation. But each has its quirks. I really wish the documentation would be a bit simpler. Especially, the customisation of table-names, is a bit problematic. My tables used con_tablename method, where the prefix describes various general usage (like auth_ for authorisation stuff, loc_ for localisation, con_ for content related). I tried to create cross tables, according the rules described (like con_items_con_persons) which gets wierd somehow. After adding the cross-tables and preparing some simple join's -even with the table-name settings, I got stuck. Table names, model names and object names got easily overlapped, resulting with false prefixes on the ID fields (e.g. it tried to use on_items_con_persons.item_id where it should use on_items_con_persons.con_item_id). I ofcourse had all tables named accordingly, used the settings array on creation etc.

The settings table/name/field_id aren't easily understandable, there should be one example for each. It is slow to try figuring out various methods.
Also the singular/plural methodology is a bit weird, i prefer to name the table names plural and the models singular. But this feature, combined with the _ names, gets easily problematic.
As a novice user, I also get troubled, when I see examples like
habtm:
name: projects
join_table: project_assignments
without some detailed descriptions.

Of course, it is painful, to create the library, prepare the docs and give support at the same time. I wish, I could help you anyhow to write examples at least, but my knowledge is limited to what I gathered from expoerimentations with the clues (not description) I saw on the docs.

I wish, that this library gets a fully-fledged alternative database-layer for CI. I am open to some restrictions (like dropping PHP4 for sake of faster development). But the possibilities should be much better documented. This library would push the whole CI much further, as CI is about speeding the development process... Again, thanks a lot and looking forward for the final release of 1.0 (following the SVN, surely).

note: after some thoughts, i believe a global setting for prefixing table/field names would be an ideal solution for me and similar-minded users.