Readit NewsIs it due to some (technical) reason that would require a monetary compensation to be profitable?
SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.
We implement providers when a paying customer requests them (Team plan for OIDC-compatible providers, Growth plan for everything else, including SAML). Once we've implemented them, though, everyone benefits.
To our surprise, as of right now we haven't received any requests for SAML from our customers.
CREATE TABLE states (
state order_state PRIMARY KEY,
depth int NOT NULL,
UNIQUE(state, depth)
);
CREATE TABLE transitions (
start_state order_state NOT NULL,
event order_event NOT NULL,
end_state order_state NOT NULL,
start_depth int NOT NULL,
end_depth int NOT NULL,
CONSTRAINT transitions_start_depth_correct
FOREIGN KEY(start_state, start_depth) REFERENCES states(state, depth)
ON UPDATE CASCADE,
CONSTRAINT transitions_end_depth_correct
FOREIGN KEY(end_state, end_depth) REFERENCES states(state, depth)
ON UPDATE CASCADE,
CONSTRAINT transitions_depth_increases CHECK(end_depth > start_depth),
PRIMARY KEY(start_state, event)
);
fsm=> CREATE DOMAIN order_state AS text;
CREATE DOMAIN
fsm=> CREATE DOMAIN order_event AS text;
CREATE DOMAIN
fsm=> -- "CREATE TABLE"s as above, then:
fsm=> INSERT INTO states(state, depth) VALUES('start', 1), ('a', 2), ('b', 2), ('done', 3), ('error', 3);
INSERT 0 5
fsm=> INSERT INTO transitions(start_state, event, end_state, start_depth, end_depth) VALUES('start', 'A', 'a', 1, 2), ('start', 'B', 'b', 1, 2), ('a', 'B', 'done', 2, 3), ('b', 'A', 'done', 2, 3), ('a', 'A', 'error', 2, 3), ('b', 'B', 'error', 2, 3);
INSERT 0 6
fsm=> UPDATE states SET depth = 4 WHERE state = 'error';
UPDATE 1
fsm=> TABLE transitions;
start_state | event | end_state | start_depth | end_depth
-------------+-------+-----------+-------------+-----------
start | A | a | 1 | 2
start | B | b | 1 | 2
a | B | done | 2 | 3
b | A | done | 2 | 3
a | A | error | 2 | 4
b | B | error | 2 | 4
(6 rows)
fsm=> UPDATE states SET depth = 2 WHERE state = 'error';
ERROR: new row for relation "transitions" violates check constraint "transitions_depth_increases"
DETAIL: Failing row contains (a, A, error, 2, 2).
CONTEXT: SQL statement "UPDATE ONLY "public"."transitions" SET "end_state" = $1, "end_depth" = $2 WHERE $3::pg_catalog.text OPERATOR(pg_catalog.=) "end_state"::pg_catalog.text AND $4 OPERATOR(pg_catalog.=) "end_depth""
fsm=> INSERT INTO transitions(start_state, event, end_state, start_depth, end_depth) VALUES('done', 'AGAIN!', 'start', 3, 1);
ERROR: new row for relation "transitions" violates check constraint "transitions_depth_increases"
DETAIL: Failing row contains (done, AGAIN!, start, 3, 1).
I think Claude has better writing style, and it's refreshing not having to fight with the thing to get it to give me full code snippets. I also hate how difficult it is to get the arrow keys to scroll up or down on chatgpt.
(https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-s3...)