Firstly, I want to give credit to the contributors for project, it’s exactly what I’ve been looking for!
Hands on control instead of being dragged into restricted eco systems like Xano/Supabase etc…
I have a use case I would like to verify if I’m attempting correctly, or if there’s an error/bug.
I have created a Many to ANY field in our notes table.
The table has “text” for the note text, and the Many To Any called “related_to”
The Many to ANY field allows relationships to our clients, projects, tasks etc…
This field is used so we can create notes/chat against other records.
It creates the table “notes_to_records”
The issue comes when I go to the client record, create the one to many field to view the notes related, it fails to create the column in the PG table. (all other many to work)
I’m not 100% here but almost positive that when you have a field configured as a Many-to-Any relationship, you can’t add additional One-to-Many or Many-to-One relationships on those same specific fields at the moment.
Will ask our team for clarification.
This is because the Many-to-Any relationship is basically a “virtual” relationship uses a junction table structure that’s different from other relationships. The junction table handles the polymorphic connections and the fields are structured a bit different than a M2M or O2M / M2O relationship.
For stuff like tasks, notes, or projects, I usually create either One-to-Many relationships or Many-to-Many relationships using a junction table if I need to connect them to multiple collections.
What specific use case are you working on? Happy to help you think through the best approach.
