Re^3: Perl Typeless Database

True, all to true, but when I put something in a database, I expect to find it back. It is bad enough as it is that probably no complex piece of software is without bugs, but deliberately adding unreliability is too much if you ask me.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Comment on Re^3: Perl Typeless Database

Replies are listed 'Best First'.
Re^4: Perl Typeless Database by tomazos (Deacon) on Jul 02, 2005 at 14:09 UTC
Of course I don't mean that the database isn't reliable in that sense. When I speak about reliability, I mean the extent to which the system tolerates a developer or user error. If a developer or user makes a mistake then a less reliable system ungracefully falls over. A reliable system catches the error as soon as possible. One of the advantages of typing is that it catches garbage data earlier, when you try to assign a value of the wrong type. A typless system happily takes the data into the system, causing problems later. Andrew Tomazos \| andrew@tomazos.com \| www.tomazos.com	[reply]

Replies are listed 'Best First'.

Re^4: Perl Typeless Database
by tomazos (Deacon) on Jul 02, 2005 at 14:09 UTC

When I speak about reliability, I mean the extent to which the system tolerates a developer or user error. If a developer or user makes a mistake then a less reliable system ungracefully falls over. A reliable system catches the error as soon as possible.

One of the advantages of typing is that it catches garbage data earlier, when you try to assign a value of the wrong type. A typless system happily takes the data into the system, causing problems later.

Andrew Tomazos | andrew@tomazos.com | www.tomazos.com

[reply]