General information
Category:
Coding, syntax & commands
can you safely use a key here ?
I am concerned that the table may change over the years, and keys get re-used!
The keys may have to control both current and archival data, but the system may not have the archive data available all the time! ( either a value may get two keys, or one key may refer to two values , unless you keep a table with all keys that have been created and their value, a serious problem if you get audited 5 years down the road! )
I suspect that there is no ultimately no safe way to control a big field with a small one!
However, if you use a simple hex look up system, you get far more mileage from your 6 byte field!
( create a look up table that stores all used strings to a new hex value, , thus using all 255 values instead of just the commonly used 10 numeric + 26 or 52 alpha, thus the field can hold about 30,000,000,000,000 ( 256 ^ 6) values, which should be enough! )
The math isn't confirmed, but I hope you get the ideas & concerns
Mike
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only