◆ Amazon DynamoDB

Query DynamoDB with case-insensitive conditions

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to query the 'UserProfiles' table for all users whose 'username' attribute contains…+
I need to query the 'UserProfiles' table for all users whose 'username' attribute contains 'john' regardless of case. Return the 'userId' and 'email' for these users. The results need to be ready for the Friday morning sync with the sales team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I run this query for the 'UserProfiles' table, I need to make sure it's efficient for…+
Before I run this query for the 'UserProfiles' table, I need to make sure it's efficient for case-insensitive searches on the 'username' attribute. Surface any potential performance bottlenecks or recommended index changes, and flag what might make this query slow down the production system during peak hours.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe last case-insensitive search for a username in 'UserProfiles' just timed out during the…+
The last case-insensitive query for user profiles timed out during a critical demo.
The last case-insensitive search for a username in 'UserProfiles' just timed out during the investor demo, and now the CEO is asking why. I used a 'contains' filter, but it's clearly not scaling. I'm afraid of impacting production or getting another timeout. Is there a better way to handle case-insensitivity without scanning the whole table? What's the best next move to get reliable results by end of day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I need to do a case-insensitive search on user data, I waste hours trying to…+
Case-insensitive searches consistently cause performance issues and anxiety.
Every time I need to do a case-insensitive search on user data, I waste hours trying to optimize the query or deal with performance complaints. It's a constant source of stress, and I keep losing credibility with the product team when these searches fail. What habit should I change to make case-insensitive querying reliable and performant from the start, instead of scrambling every time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.