Hey YXDB Bosses,
Let's move forward with our YXDB. Maybe give AMP a real edge over e1. Here are some things that could may YXDB super-powered:
- Metadata
- Workflow information about what created that poorly named output file.
- When was the file originally created/updated.
- SORT order. If there is a sort order for the data, what is it?
- Other stuff
- INDEX. Currently you get spatial indexes (or you can opt out). If I want to search through a 100+MM record file, it is a sequential read of all of the data. With an index I could grab data without the expense of a calgary file creation. Don't go crazy on the indexing option, just allow users to set 1+ fields as index (takes more time to write).
- I'm sure that you've been asked before, but CREATE DIRECTORY if the output directory doesn't exist.
- Old School - Crazy Idea
- Generation Data Groups (GDG)
This will likely make @NicoleJ 's eyes roll 🙄 but back in the days, we could write our data to the SAME filename and the old data became 1 version older. You could read the (0) version of the file or read from 1, 2, 3 or more previous versions of the data using the same name (e.g. .\Customers|||3). The write of the output file would do all of the backing up of the data (easy to use) and when the initial defined limit expires, the data drops off.
Just a little more craziness from me
cheers
