brick / orm Goto Github PK

We now have support for JSON columns, but it would be interesting to support storing a property into a string column as a serialized string as well.

JSON is good for a lot of use cases, but it cannot unserialize to custom classes.

When finding an entity that has child classes, we need to perform a WHERE IN() with the discriminator value of the entity class AND those of all its subclasses.

Currently, only the dicriminator value for the class itself is requested.

Apart from the title,

Thanks for this!! I was wondering why aren't more people making this happen, using PHP 7.4 typed properties is an absolutely fantastic idea!!

Would it be as easy as writing models like?

 class Person{
    integer $id;
    string $name;
    Country $country;
  }

it would be nice if all tables were autogenerated (like spring-boot and grails etc),

and the usage would be as easy as:

 $p = new Person("John", Country.findByName("Australia"));
 $p.save();  // or PersonRepo.save($p)
 PersonRepo.get(1)
 Person.get(1) //even better

other variations:

CountryRepo.findByIdAndName(3, "Australia");
CountryRepo.findByNameLike("Aus%");
CountryRepo.findAllByNameIn(["Korea", "Japan", "Australia"])

GORM(Hibernate based) is one of the best ORMs from the Java/Groovy world, would be nice if can copy those features:
http://gorm.grails.org/latest/hibernate/manual/index.html

Would be interesting to see how it integrates with laravel (I'd rather use PDO than use Eloquent )

If setIdentityProperty() has not been called after addEntity() during configuration, and the entity has an id property that's an int or a string, consider it an auto-increment identity field by default.

This will prevent overly verbose configuration files as most entities have such an ID.

Several databases now have first-class support for JSON, allowing to store whole entities as JSON documents, like in a NoSQL database.

We do have support for individual JSON columns, but it would be interesting to add support to store a whole entity (all properties) as a single JSON column.

The table would look like:

id   INT PRIMARY KEY
data JSON

It should be possible to mix entities mapped in a typical object-to-relational way, and entities mapped to JSON, in the same application, with support from this library.