- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
But does it have the frist digit?
Admin
Remy, stop trying to make "performant" happen. It's not going to happen.
Admin
The dry wit is strong with this one.
Admin
UUID() built-in is available in most DBs...
Admin
It's already in a dictionary... https://dictionary.cambridge.org/us/dictionary/english/performant
Admin
But not many.
Admin
It is bad grammar to say one of those data warehouse tables that exists to make queries performant. You want to say EXIST, because you're describing the class of tables. If you don't like comments about bad grammar, don't use bad grammar.
Admin
"Remy, stop trying to make "performant" happen. It's not going to happen." You can have fast, good and cheap. Pick two out of the three.
Admin
It's in the OED...
Admin
The word "performant" was a word meaning one who performs a ceremony, etc. (Compare with "celebrant", which is one who celebrates.) So it's definitely a word, though obsolete.
As an adjective, it's much more recent, but it is used, and it's in the OED.
Admin
The LEFT JOIN is O(N) (well, okay O(N+M)). Let's assume enforcement of 1,000 unique ID's is the aim and we're allowed to not include the non-numeric values in our table... The design is kind of tricky and depends on usage, especially if you want excellent peformantness. Biggest issues are fragmentation (like when using two tables for the approach) and read/write contention.
Admin
Am I to understand that you haven't seen Mean Girls?
Admin
lol