But will the AI ask you to clarify the question when you give it some natural language that is (humanly) ambiguous, or will it take the text as given?

(Thinking messy combination of ANDs and ORs - will the AI simply use logical precedence, or will it ask for clarification on bracketing?)

Unfortunately it's not documented and the suggestive "reset_value" column was blank for all the options I tried - but at least the names are there.

It's not the vax it's the cat.

You may think it spends all its time scratching you but those are hypodermic claws injecting nanites that can draw power from the electrical signals to and from your brain. What else could make you put up with the way it treats you.

2/2

Quoting 2016
"It's an interesting observation that the Windows implementation is inherently slower but scales better because of the randomness while the Linux version is inherently faster but suffers significant index contention at higher concurrency. This type of reversal isn't uncommon ..."

1/2:
A comment I made in a discussion on the Oracle Forum about sys_guid() several years ago forums.oracle.com/ords/apexds/... - the Windows and Unix implementations are (were?) completely different, leaving the Unix one highly sequential and the Windows one extremely random:

The size of the PK index for v7 was also worth investigating - 600M for 10M rows => 60 bytes per row. The same index would be about 300M in Oracle unless the UUID "type" was actually the character representation including hyphens, or the index suffered 50/50 leaf node split all the way through.

I've read the linked article on testing uuid-7 vs. uuid-4 under Postgres, and it prompted a few questions that would make me very cautious about using the Postgres results as a basis for any Oracle decision.

The strangest detail was the difference in "plan time" between them for "id = constant"!

Umbrellas - to help you avoid the side effects of clouds?
And it looks like you've got the multi-cloud option there.

Coincidentally I've been looking at hybrid histograms in the last couple of days and started sketching some notes about the factors involved in calculating join cardinalities for two tables with four join predicates and a couple of non-join predicates.

Then I realised how much work that would be!

But will it be a deep dive session?

Unfortunately the OVM version is only 23.9 - with all the Developer/ORDS/etc. stuff - not a "23.26"