The following shows the right and wrong way to specify the environment flags. Be careful using
Key: Value format depending on the docker version.
version: "3.2" services: mariadb: image: mariadb:10.5 ports: - "3306:3306" environment:
|create table test(id int, b blob);|
|insert into test(id, b) select 1, 0x000000;|
|insert into test(id, b) select 2, 0xffffff;|
|create function set_bit(b blob, pos int, val int) returns blob reads sql data|
|comment 'changes the bit at position <pos> (0: right most bit) to <val> in the blob <b>'|
I have a pretty constant-use case in mind for collecting client metrics with different loads and spikes throughout the day and am mostly interested in paying a little extra to not have to manage the RDS/Aurora server instances. I basically just need a k/v store but need to do report queries/scans so DynamoDB isn’t a good fit. (COUNT(*) FROM, SUM, etc..)
Looks like a minimum of 5 minutes of usage each time the database is activated and I’m pretty sure my load will never let the database shutdown so that might solve the cold-start issue.