3 ms·
Thanks for the detailed response. I had guessed at your approach, and I wasn't too far off it seems. Moving the processing to the software level (rather than s
by magicalhippo 4y ago
Thanks for the detailed response.
I had guessed at your approach, and I wasn't too far off it seems. Moving the processing to the software level (rather than staying in the db layer) makes sense.
A challenge we have is that for many of our UIs, we have very wide rows. Our main "offender" has over 100 fields on the main page, and that table also has several 3-4 level deep child tables.
Would be interesting to see how it would perform using your approach. I might just have found another summer vacation project, just for fun...
Not that I think it would work for us, like I said we rely on multi-column indexes for performance and consistency so that's probably a show-stopper right there. But I do like to try different approaches just for the experience.