Re: MySQL and perl? Or something else?

but with the hypothetical user constantly adding new fields within new fields within new fields, ...

Duh? How the heck are you organizing your data structures? I can see no reason to indefinitely nest fields. But maybe that's just me.

Can you expand on how you see these things? (Newbies often have a refreshing new look on old problems, unhindered by tradition, so that's why I'm curious.)

Comment on Re: MySQL and perl? Or something else?

Replies are listed 'Best First'.
Re^2: MySQL and perl? Or something else? by Andrew_Levenson (Hermit) on Mar 15, 2007 at 18:17 UTC
It would be indefinite because the user would have the ability to create new fields of information, and new fields could beget new fields. i.e. One person has multiple web addresses, the user could categorize them under "web addresses," a field they add in, under which could be sub-categories "work," "personal," etc. `C(qw/74 97 104 112/);sub C{while(@_){$c**=$C;print (map{chr($C!=$c?shift:pop)}$_),$C+=@_%2!=1?1:0}}` [download]	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: MySQL and perl? Or something else?
by Andrew_Levenson (Hermit) on Mar 15, 2007 at 18:17 UTC




C(qw/74 97 104 112/);sub C{while(@_){$c**=$C;print
(map{chr($C!=$c?shift:pop)}$_),$C+=@_%2!=1?1:0}}
[download]

[reply]
[d/l]