Hacker Newsnew | past | comments | ask | show | jobs | submit | username1407's commentslogin

Me neither, and thanks to Apple’s idiotic thought of 1 country = 1 language I’m not even allowed to read it my the language of choice. Thanks Apple!


I'm sure Apple have the utmost respect for their users, and the internal decisions that led to this design choice answered the questions "what does the customer need?" and "how can we help them be more productive?"


I've read the landing page and I have no idea what this does or who the target audience is.


If I understand correctly, and @mpetyak can correct me if I'm wrong: writing prompts for GPT-3 is something of an art. This lets you save your prompts, and lets other people execute them, to see what GPT-3 comes up with. It even supports fields for the end user to fill in, so they can see the output without having to worry about what the prompt was.


Thanks egonschiele, I would say your summarisation is quite accurate :) There is definitely more work to be done on the positioning/landing page text, I do hope that the service will grow into something more general than just GPT-3 prompt organising and sharing, but should maybe keep it more grounded/specific for now


Can't you use json operators [1] for this?

-- Permanently delete message sent by jon

DELETE from deleted_record where table_name = 'messages' and data->>'sender' = 'jon';

[1] https://www.postgresql.org/docs/15/functions-json.html


That assumes that all of a user's data is a single foreign key relationship away from the user, which often isn't the case.

It also requires you to scan the entire table and decode JSON for every row you've ever deleted, which may become prohibitively expensive for large databases.


PostgreSQL can create indexes on the results of expressions, so it's possible to accelerate queries that select against a nested value inside a JSON blob.


That's true.

To give an example for your 1st point: If you have the schema users->messages->message_attachments and message_attachments does not store the user_id, you'll have trouble finding all attachments from a specific user.


The deletion table is a schemaless table, it may become hard to anonimize the data


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: