If you know you are at risk for specific cancers, then you would likely get tested more regularly and could potentially catch them at an earlier stage when they're usually more treatable.
I haven't looking into this specifically, so I have no idea if that works for the types of cancers this tests for. My point is applies to testing just generally speaking
You can make a REST endpoint match a client's needs, but if you have multiple clients (for example, 1 for mobile and 1 for desktop) that all need different amounts of data (for example, the mobile client shows a simplified view with less data), then you would need to write 2 different REST endpoints to handle each clients. Multiply that by the number of pages with a difference.
Since we're here talking about Postgres and SQL standards. Here's my wishlist:
- Support for arrays of foreign keys. This one has been worked on a couple of times but hasn't made it into a release. https://commitfest.postgresql.org/17/1252/ - I think this would be an absolutely phenomenal way of handling sorting, instead of having to use linked lists and CTEs or some type of "order/position" column
- Support for deferring NOT NULL and CHECK constraints to the end of a transaction (just ran into this problem yesterday)
> - Support for deferring NOT NULL and CHECK constraints to the end of a transaction (just ran into this problem yesterday)
I'm curious what the use case of this is?
Deferrable constraints are usually considered for foreign keys, since there you might have to juggle updates to multiple tables and might violate the constraint in the intermediate states. But that doesn't appear to apply in that way to CHECK constraints.
The sites are deployed on Vercel and Digital Ocean. Both platforms allow users to connect their custom domains, and they auto-generate the SSL for these domains.
Adding systems in place to handle unsubscribing from transactional emails will mean quite a bit of engineering time/effort for many companies.