date-time VS Brick\Math

brick/date-time: Date and time library for PHP

brick/date-time: Date and time library for PHP

If you're happy to bring in another library, you could replace your Date VO class with the LocalDate class from the brick/datetime library. It does the same thing, just has three int fields inside instead of a string in Y-m-d format.

If you need to store subsets of a date-time-timezone combination, then take a look at brick/date-time instead.

Slightly related but https://github.com/brick/date-time is a wonderful library to manage datetime concepts in a proper way.

Looks like a CivilDate is the same thing that brick/date-time calls a LocalDateTime. Does this library have any advantages over the one from Brick?

I like https://github.com/brick/date-time

It is a good practice to use an interface to manage the clock in an application, as it allows having full control of time. For example, it eases testing, as it lets us define the concrete time for each test. Frank de Jonge and Matthias Noback have blog posts about it, brick has an implementation, and there is even a PSR proposal to have a ClockInterface.

brick/math: Arbitrary-precision arithmetic library for PHP

Use strings. For PHP specifically, the Brick/Math library.

There are excellent wrappers for this like https://github.com/brick/math

https://github.com/brick/math to handle bignumber and operations

In Java and Ruby, BigDecimal is an inbuilt class that can be used. For PHP, you can checkout the Brick Math Library Basically, just find the arbitrary-precision Decimal type/Class/Library in your choice of language. Got another approach, please do let me know in comment section.

I decided to use https://github.com/brick/math and store the amount as a string in the database. My project use NANO, so that's 30 decimal points to keep. Number type column is not the choice at all.

There are many use cases where enums don't need to be backed by a scalar. I'm thinking of brick/math's RoundingMode for example: you use these in code, but never store/serialize them really.

Besides, using an arbitrary-precision library gives you an unlimited number of digits, and, in the case of brick/math, many more rounding modes to choose from. And predictable ones.