rand(Ø)

> beautiful code & photos

about <

Posts tagged: protip

MySQL: Table count for all databases

By Joris Berthelot Published February 22nd 2018 Tagged mysql, protip, sql, database, english, count, table

Answers I found on the internet were all based on the table information_schema.tables but truth is, this table contains table schemas of databases, not the database list.

What happens when you also need to include databases with no table?
Answer with this query:

SELECT SCHEMA_NAME AS 'Database', COUNT(information_schema.tables.TABLE_SCHEMA) AS 'Table Count'
FROM information_schema.SCHEMATA
LEFT JOIN information_schema.tables ON information_schema.tables.TABLE_SCHEMA = information_schema.SCHEMATA.SCHEMA_NAME
WHERE SCHEMA_NAME NOT IN ('mysql', 'information_schema', 'performance_schema', 'tmp')
GROUP BY SCHEMA_NAME;

+----------+-------------+
| Database | Table Count |
+----------+
> Continue Reading

Chakram & JSON schema structuring

By Joris Berthelot Published February 12th 2018 Tagged javascript, nodejs, protip, json, json-schema, chakram, mocha, functional testing, schema, testing

I know, Chakram is old (no update over a year) but I use it in one of my project because along with Mocha and Chai, it makes a pretty powerful tool for a NodeJS functional testing stack.

For the past few hours, I've been trying to reference a JSON schema from another one stored in the very same directory.

Understanding the documentation about structuring JSON schema is pretty straightforward but in real life, it gets more complicated when you don't fully understand how it really works (and I still don't, don't get me wrong).

The issue

Let's say, I have

> Continue Reading

AWS ECS: seamlessly handle app versioning

By Joris Berthelot Published January 29th 2018 Tagged aws, amazon aws, docker, go, golang, versioning, ecs, container, aws ecs, semver, protip, cloudop, deployment, ci

Our latest project at work involved another Go API and in the effort of easing our debugging and issue tracking I'm used to inject the app version into the logs.
It helps a lot monitoring, especially when rolling out a new version (canary, 50% traffic deployment, etc.).

Preamble

Pre-2018, I hardcoded the version in an app constant which I would increment as part of my release process. It's easy, quick but the only issue is to not forget about it because you may lose versioning syncing over time.

Plus, considering this to be done before each new release, this adds

> Continue Reading