in reply to Re^2: key value in text format
in thread key value in text format

That just raises the DB requirements and puts any text file based solution right out of the running. The solution is essentially the same, but use one of the other DBD:: modules to access your database of choice. Once you get beyond simple requirements that can easily be met by SQLite you will find fairly strong division between proponents of different databases.

The saving grace is that you can do a lot of development against DBD::SQLite then migrate to using the more serious database of your choice when the system needs to hit the NFS.

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

Replies are listed 'Best First'.
Re^4: key value in text format
by pwagyi (Monk) on Nov 07, 2019 at 05:57 UTC

    Guess I'll use DBD::SQLite during development and switch to DBD::mysql for production use.

[reply]
      Please, use DBD::MariaDB instead of DBD::mysql to prevent hair loss.

      map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
[reply]
[d/l]

        And here begins the "fairly strong division between proponents of different databases" :-D.

        Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
[reply]

In Section Seekers of Perl Wisdom