5 Commits

Author	SHA1	Message	Date
Lucien Cartier-Tilet	19284665e6	feat: implement preliminary composite primary key support ... Add support for entities with composite primary keys using multiple #[georm(id)] fields. Automatically generates {EntityName}Id structs for type-safe composite key handling. Features: - Multi-field primary key detection and ID struct generation - Full CRUD operations (find, create, update, delete, create_or_update) - Proper SQL generation with AND clauses for composite keys - Updated documNtation in README and lib.rs Note: Relationships not yet supported for composite key entities	2025-06-09 22:41:39 +02:00
Lucien Cartier-Tilet	aafbfb7964	feat: add foreign one_to_one relationships	2025-06-07 15:42:31 +02:00
Lucien Cartier-Tilet	b70b4b7a81	test: added tests for M2M relationships, it works	2025-01-31 23:14:40 +01:00
Lucien Cartier-Tilet	86e29fa2dc	test: one-to-many relationships work	2025-01-31 23:14:40 +01:00
Lucien Cartier-Tilet	bca0619f30	fix: simple ORM for one struct and foreign references work ... Currently, all methods declared in the Georm trait are available. If a struct has an ID pointing towards another entity, the user can create a get method to get the entity pointed at from the database too (local one-to-one relationship). I still need to implement remote one-to-one relationships (one-to-one relationships when the ID of the remote object is not available locally). I still need to also test and debug one-to-many relationships (ID of the remote entiies not available locally) and many-to-many relationships (declared in a dedicated table). For now, IDs in all cases are simple types recognized by SQLx that are not arrays. Options are only supported when explicitely specified for one-to-one relationships.	2025-01-31 23:14:39 +01:00