-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Moin,

On Thursday 13 July 2006 19:40, A. Pagaltzis wrote:
> * Tels <[EMAIL PROTECTED]> [2006-07-12 19:00]:
> > Using SQLite or similiar is what really creates the problems
> > with CPANTS - you cant just access the raw database without the
> > front-end.
>
> All you need is one binary from www.sqlite.org – I don’t follow
> why this is a problem. And I certainly prefer talking SQL at a
> database than writing throwaway helper script code to manipulate
> serialised data structures.

But what if the DB isn't SQL? And it can change at a whim?

> > Of course for performance reasons it might not be good, but
> > since premature optimization is the root of all evil, I'd say
> > use YAML now, change when nec.
>
> Who cares about performance – I don’t want to have to write code
> to walk data structures just to ask questions about a heap of
> records. Sometimes with an in-memory data structure I resort to
> DBD::RAM instead of writing endless chains of maps, greps and
> foreach loops just because SQL is so much lazier.
>
> SQLite is a godsend. (drh++)

But how can you then switch the database backend if the user doesn't want to 
use helper scripts or the OO interface?

I see I wont ever be able to please people that prefer their access raw and 
without a layer in between then.

Best wishes,

Tels

- -- 
 Signed on Thu Jul 13 21:41:02 2006 with key 0x93B84C15.
 Visit my photo gallery at http://bloodgate.com/photos/
 PGP key on http://bloodgate.com/tels.asc or per email.

 "Those are my principles, and if you don't like them... well, I have
 others." -- Groucho Marx

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iQEVAwUBRLaiKHcLPEOTuEwVAQL2XQf+M8HAR4yC3KIIK1B3nW9bxGxPV/vX8eeR
/6v8p+/14veYWIxjwvf7OVXos0RjA0LzIvOnOzjNV1JBDmRebkhU4ago4ZGpMMkL
L6uVM1P9C4aWgTjBxKiQ3jw3+fBGBRlDBd7Z7c4nqY4wQpZg2aS85ol/u8k+39vO
gbeqzf958xy2o62g2bg7FR3l2FjR5bYM8mj+qWNzrdq2PJJOzXb7H56j+yRG9yWK
k7oH9Ce01estiigSWwCKW7UqNExk9HseC48U3QeZ8s0qrqvQBzUp8fZPX6hqgeot
uklbniT+zrw3zcexodzwzYoRJAP3PpXb84qmUmYIcliVcDJLMqrztA==
=bbQk
-----END PGP SIGNATURE-----

Reply via email to