I believe (but could be wrong) that 'tuple' in relational database terms means 'the group of columns that comprises a table', more or less.
On the basis of that definition, it would appear that you want to have a table with
one column for each element in your array. Hopefully, I've misinterpreted you, because that is not a robust architecture ... when the array grows you'd need to add new columns (when, in a relational database, adding rows is the appropriate response, which is easy).
So, here's a solution that I think would work.
Your array is three dimensional, with each dimension being indexed by an int. The index set (tuple) that identifies a specific value in the array must be the Primary Key of the database table that holds the array values; the table will have one other column that contains the value, and may have others if you need to track when and by whom values were changed.
Here's a table definition that would accomplish this:
CREATE TABLE GiveMeAMeaningfulName
(
Index1 INT NOT NULL,
Index2 INT NOT NULL,
Index3 INT NOT NULL,
Value FLOAT NOT NULL,
PRIMARY KEY (Index1, Index2, Index3)
)
GO
Note - I work with Microsoft SqlServer; my SQL dialect may not work perfectly with MySql. The idea should nevertheless be valid.
With a table design like that you are free to save all elements of your array, or just those that have changed. As with all other times when a collection must be saved to / loaded from a database, unfortunately you have to iterate through the collection to save/load each element. There may be ways to do it with a single command that deals in bulk; if there are maybe others here will offer them (and I can learn, too!).