Static lookup tables (e.g. remove MySQL)

[samatjain]

At the moment, MySQL is used to store several look-up tables.

Since this data rarely changes (it is typically updated quarterly to yearly), there's no reason for these look-up tables to be in MySQL. It needlessly complicates the server stack.

The lookup tables could be stored as JSON that are loaded by the application, or even as PHP arrays.

[ghost]

Howdy Samat! I agree that anything that uncomplicates things is a great idea. When can we get together for a check in and update? We are making progress with the Cliff Effect Memorial Task Force here in New Mexico! Peace . . . Vince Sincerely, Vince Gonzales VinceCo Technology Services for Small Business

…

On Aug 10, 2017, at 7:08 PM, uıɐɾ ʞ ʇɐɯɐs ***@***.***> wrote: At the moment, MySQL is used to store several look-up tables. Since this data rarely changes (it is typically updated quarterly to yearly), there's no reason for these look-up tables to be in MySQL. It needlessly complicates the server stack. The lookup tables could be stored as JSON that are loaded by the application, or even as PHP arrays. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHh4suFBNCS7_i5Ns_c5RBVGTltu2KaDks5sW6mUgaJpZM4O0JrU>.