Is It Viable To Have A SQL Table With Only One Row And One Column?
I'm currently working on my first application that uses a database so I'm very new to this. The database has multiple tables that are what you would expect to normally see. However
Solution 1:
What is your table storing? it's storing some kind of processing audit. So make it a little more useful - add a column storing the last datetime that the data was processed. Add a column for the time it took to process. Add another column which stores the username (or some identifier) of whoever ran the process. Now add a row for every table that is processed (there's only one now but there might be more in future). Try and envisage how your processing is going to grow in future
Post a Comment for "Is It Viable To Have A SQL Table With Only One Row And One Column?"