Saving serialized arrays vs just using the DB

h4x0rmx

Recently I've been working on a system in which there's a part that handles tests for different agents. The programmer that originally did it stored all the questions and answers (separately) as serialized arrays in the DB.
I've always tried to store everything directly in the DB thinking that if we need to move the data to another system or use it somewhere else it would be easier to do it. But by working with this system, I've realized that storing serialized arrays has some advantages since it is easier to keep track of test versions (every time the test changes, the new set of questions/answers is stored as a single record as a serialized array and it can later be compared easily) and some other things easily.
I was wondering if

you could tell me the advantages of doing/using one thing over the other
you could point me to a tutorial where a system extensively uses serialized arrays

I will really appreciate your help!

big_nerd

I can't think of a tutorial on serialized arrays myself, as I find that I put everything into separate columns in the database, as its much faster & easier to run reports in my experience.

It depends on what you are using the data for, in my opinion, serializing the arrays for storage really starts to defeat the purpose of the database, of course, this depends on the amount of data and how you are pulling it up.

From a programming standpoint its 'easier' .. only if you are lazy, I don't believe it takes THAT much time to add columns to an INSERT or SELECT statement.

I can foresee the use of serialized arrays in an XML/INI/TEXT based system, where I suppose no DB is available.

Even still its just as quick & easy to use XML / CSV functions.

Also, When I develop Applications I generally have two databases, and/or two tables (dependent on need), 1 for Production, 1 for Development.

One could also hold a column 'test' (1 or 0) that would achieve the same effect.

You can easily write (or download) a Library which will pull the columns into an array, effectively giving you the same result.

h4x0rmx

In my opinion this specific system I'm working on could have been done with more tables saving the serialized arrays for another occasion, but it is true that serialized arrays make things easier if you're lazy. This one system is somewhat slow because there's a lot of parsing going on.

I guess I won't try to learn how to use arrays.

big_nerd

h4x0rmx,

Array's are a beautiful thing if used right, I can recommend that if you read the Zend Certification Study Guide that you will learn quite a bit about them!

h4x0rmx

big.nerd;10933524 wrote:
h4x0rmx,

Array's are a beautiful thing if used right, I can recommend that if you read the Zend Certification Study Guide that you will learn quite a bit about them!

Indeed they are. I just think people need to learn when to use them.
...the other day I had to rewrite a script that read and parse a csv file and the prior programmer stored the huge file in an array and tried to parse it, killing the script because it took too much time. Instead I just read the csv it, stored it on a temporary table on the database and wrote a few functions (that manipulated arrays too 😉 ) and the script was so much faster.
(not that I'm good, but I'm learning)

Thanks big.nerd, I will read that part of the Certification Guide (I have it, haven't read it all though)

Weedpacket

http://asktom.oracle.com/pls/asktom/f?p=100:11:0:::😛11_QUESTION_ID:6692296628899

h4x0rmx

Weedpacket;10933529 wrote:
http://asktom.oracle.com/pls/asktom/f?p=100:11:0:::😛11_QUESTION_ID:6692296628899

@: nice!
Thanks!!!