Re: postgres vs Mysql
From: Pham Nuwen (pham.nuwen3d6_at_libertydice.org)
Date: 11/21/03
- Next message: Google Mike: "HOWTO: FreeTDS for Newbies (almost complete)"
- Previous message: Tim Tyler: "Re: error_reporting (E_ALL);"
- In reply to: Michael Fuhr: "Re: postgres vs Mysql"
- Next in thread: OneSolution: "Re: postgres vs Mysql"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 21 Nov 2003 19:31:36 GMT
Michael Fuhr wrote:
> Could you elaborate on what "dumb ass perl programmers" are doing
> that results in data corruption?
In our db the original contractor who programed this monstrousity
managed to build a table that takes logdata from one set of (DBF) files
and imports it into a table. Instead of doing this the intelligent way
with a proper table, he instead built a vertical monster that looks like
this (greatly simplified):
recordsetnumber | field | value | timestamp
========================================
1 aa 1 12:01
1 ab 3 12:01
1 aa 2 12:02
1 ab 5 12:02
2 aa 3 12:01
etc....
All in all not a mortal sin (ugly and stupid but not a sin), except that
the timestamp that obviously has to be the unique key, was not produced
on the backend but taken from the client end in a user edititable field.
Thus the data now has no integrity. No actual data loss, just a UGLY
mess, that I'm having to support and clean up.
> What, if anything, are they doing that "dumb ass [pick any language]
> programmers" couldn't do?
Nothing it just happened to be perl in this case. However it did does
stem from a particular attitude I personally have found to be fairly
unique to the perl programmers I've meet. I don't mean to dispariage all
perl programmers, nor do I think any one language is better or worse
than another, but in my own experience I have found that many perl
programmers are far too lax about data integrity, and security. They
tend to spend more time making an unreadable mess, and vastly more
complicated program, than the task requires. I think it comes from the
web-programming attitude, of "well if that doesn't look right, we can
change it, and we don't have to worry about what it used to look like".
In my case however what it did look like is all too critical.
> In other words, is the language they're using really relevant?
Nope.
-- /---+----+----+----+----+----+----++----+----+----+----+----+----+---\ I pham.nuwen3d6@libertydice.org II No nation was ever ruined by I I http://www.libertydice.org II trade, even seemingly the most I I remove "3d6" to e-mail II disadvantageous. - Ben Franklin I \---+----+----+----+----+----+----++----+----+----+----+----+----+---/
- Next message: Google Mike: "HOWTO: FreeTDS for Newbies (almost complete)"
- Previous message: Tim Tyler: "Re: error_reporting (E_ALL);"
- In reply to: Michael Fuhr: "Re: postgres vs Mysql"
- Next in thread: OneSolution: "Re: postgres vs Mysql"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|