hartraft

PostgreSQL is Enough

Background and Cron Jobs

Postgres

Index Json data in Postgres (Scalegrid)
JSON in PostgreSQL (Cybertec)
Postgres FTS (Crunchydata)
When to avoid JSONB in a Postgres schema
PostgreSQL JSON (Instaclustr)
Oleg's FOSDEM 2021 speeding up JSONB in Postgres talk
[Oleg's PGConfEU 2012 talk FTS in

We want PlanetScale to be the best place to work. But every company says that, and very few deliver. Managers have a role in creating an amazing work experience, but things go awry when the wrong dynamic creeps in.

We have all seen those managers who collect people as “resources” or who control information as a way to gain “power.” In these cultures, people who “can’t” end up leading the charge. This is management mediocrity.

What will make us different? At PlanetScale, we won’t tolerate management mediocrity. We are building a culture where politics get you nowhere and impact gets you far. Managers are here to support people who get things done. They are as accountable to their team as their team is accountable to them.

We evaluate managers on the wellbeing and output of their team, how skillfully they collaborate with and influence others, and how inclusively and transparently they work.

You can expect your manager to:

Perceive a better version of you and support you in getting there

1. Clone your fork:

git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

Service	Type	Storage	Limitations
Amazon DynamoDB	⚠️ Proprietary NoSQL	25 GB	⚠️ Payment method required
Amazon RDS	⚠️ Proprietary RDBMS		⚠️ Only free for 1 year
Azure SQL Database	MS SQL Server		⚠️ Only free for 1 year
👉 Clever Cloud	PostgreSQL, MySQL, MongoDB, Redis	256 MB (PostgreSQL)	Max 5 connections (PostgreSQL)

	sudo apt-get update
	sudo apt-get install -y python3 python3-dev python3-pip gcc
	sudo apt-get install -y python3-opencv
	sudo apt-get install -y python3-numpy
	sudo apt-get install git
	sudo apt-get install wget
	sudo apt-get install python3-setuptools
	wget https://github.com/rockchip-linux/rknpu2/raw/master/runtime/RK356X/Linux/librknn_api/aarch64/librknnrt.so
	sudo mv librknnrt.so /usr/lib/librknnrt.so
	git clone https://github.com/rockchip-linux/rknn-toolkit2.git

Service	Type	RAM	Storage	Limitations
👉 Adaptable	PaaS	256 MB	Non-persistent? (1 GB database storage available)
AWS EC2	IaaS	1 GB		⚠️ Only free for 1 year

	node {
	echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1'
	echo 'No quotes, pipeline command in single quotes'
	sh 'echo $BUILD_NUMBER' // 1
	echo 'Double quotes are silently dropped'
	sh 'echo "$BUILD_NUMBER"' // 1
	echo 'Even escaped with a single backslash they are dropped'
	sh 'echo \"$BUILD_NUMBER\"' // 1
	echo 'Using two backslashes, the quotes are preserved'
	sh 'echo \\"$BUILD_NUMBER\\"' // "1"

	If you use the findAll(Specification, Pageable) method, a count query is first executed and then the
	data query is executed if the count returns a value greater than the offset.

	For what I was doing I did not need pageable, but simply wanted to limit my results. This is easy
	to do with static named queries and methodNameMagicGoodness queries, but from my research (googling
	for a few hours) I couldn't find a way to do it with dynamic criteria queries using Specifications.

	During my search I found two things that helped me to figure out how to just do it myself.

	1.) A stackoverflow question.

	#!/bin/sh
	#
	# Automatically adds Jira key to commit message
	#

	if [ -z "$BRANCHES_TO_SKIP" ]; then
	BRANCHES_TO_SKIP=(master develop)
	fi

	BRANCH_NAME=$(git symbolic-ref --short HEAD)