Enchantment_of_Nyx
Literotica Guru
- Joined
- Mar 22, 2020
- Posts
- 1,427
Uh, the field names would be good but they don't really tell you squat, you need the table names and the dependencies. And who knows what they names used way back when the entire thing was created.
A long, long time ago, in a land far, far, away... Chicago to be exact. The company I worked for was called in to fix a problem with a system for a client. We threw our hands up and gave the guy his retainer back. What he had brought from some other "guy" wasn't an standard database but had to be called 'Bob's Database' None of the column name made sense and he had embedded code in the table columns. It was a complete mess.
I've had the opposite experience. When, in my line of work, I look for information that people don't want me to have, they often foolishly give me something where only the field names are there. (Because they've run a query on the database in a way that ensures no results.) You'd be surprised how much use I make of those things. They are the first crack in the wall.
I'm not sure how helpful dependencies would be to me or how many there would be for this type of thing, but I'd love to see the field properties. But, like I said, I'd love to see the whole thing. Sadly, nobody seems to be offering me any of those things. But if anyone ever takes my order, I'll ask for a side of table dependencies for you if you promise to share.