Just got a quick question about managing relationships in the same model but it's a bit weird.
I have user, account, account_mgr, and services table, as well as dedicated models (3) for each. This is because services are static and I store extra information in the account_mgr table about each service.
So a user has account(s) (1:M) with a dedicated joining table. The account has services attached to it via the account_mgr dedicated table to the services id with account specific settings stored as extra fields in the account_mgr table.
Is it possible to store the foreign keys (user id) in the dedicated join table (account_mgr) to do same model relationships such as creator of the service. NOT the service it self(services), but the account_mgr table.
When ever I create this relationship between account_mgr and user (as created/creator) it always tries to use a dedicated joining relationship table.
Ignore that one ahaha. After a bit more doc reading and fiddling I see that DMZ looks for the field first, then looks for the table. Was using the incorrect naming in account_mgr so was not working properly. Works great now
EDIT:
Also, as a note, when ever I try to create same-model relationships. Ie user/creator/created on the same table I want to know if it's possible to store the keys in the user table as well, instead of a dedicated joining table.
So I can call $u->creator->get()->username; and store the creator's ID as a field against that user ($u) in the same table.
EDIT 1.2
Because right now I have a dedicated joining table for this named pure_createds_creators (pure_ is table prefix) which just doesn't seem right.. What step am I missing here
Any help is much appreciated.
I've got this working in table too, however when I call