The problem is the version tracking - assigning authorship to the differences between records - since no matter how normalized a record (table row) is, it might always have a number of authors. OTOH, this tracking/auditing must not obfuscate the record text (inline tagging not feasible)
Alas, not as simple as it looks.
Unless I'm missing something, it should be simple. I know there are other solutions out there but one solution I would suggest is like so:
User enters/modifies information
User submits information to script via form
Script validates data
Script submits data to cvs
Script enters/updates data in database
Script returns canned response
Use cvs for your audit and the database for your presentation. You're duplicating data, but think of it as a cheap backup.
SCO's lawyers have forbidden the person who was going to talk to us to answer the questions we had on the grounds the answers would be used by IBM against them.
I don't think they have to worry about that... I don't think IBM really needs any help in that resepect.
He's not talking about production-candidate code, and mozilla 1.0 is stable (relatively).
But the critical code for the next revision is constantly being tweaked and improved. The beta code is sometimes b0rken for an hour or a day, but that's ok, and to be expected.
Slashdot Mirror
I like this idea. It would also answer the question of "where will the money come from", at least partially.
Wouldn't the movie industry like to see this happen?
:D Quite right.
I was doing customer support and learning unix at the same time. I forgot which shell I was in and went to delete some work files.
.* as root on a customer system.
We worked in customer systems as root (I know, I know--but I didn't even know better back then).
So, I ended up typing rm -fr *
They had no backups.
I was looking for a job that afternoon.
The problem is the version tracking - assigning authorship to the differences between records - since no matter how normalized a record (table row) is, it might always have a number of authors. OTOH, this tracking/auditing must not obfuscate the record text (inline tagging not feasible)
Alas, not as simple as it looks.
Unless I'm missing something, it should be simple. I know there are other solutions out there but one solution I would suggest is like so:
Use cvs for your audit and the database for your presentation. You're duplicating data, but think of it as a cheap backup.
Am I misunderstanding something?
SCO's lawyers have forbidden the person who was going to talk to us to answer the questions we had on the grounds the answers would be used by IBM against them.
... I don't think IBM really needs any help in that resepect.
I don't think they have to worry about that
He's not talking about production-candidate code, and mozilla 1.0 is stable (relatively).
But the critical code for the next revision is constantly being tweaked and improved. The beta code is sometimes b0rken for an hour or a day, but that's ok, and to be expected.