| From: | Guido Neitzer <lists(at)event-s(dot)net> |
|---|---|
| To: | Ted Byers <r(dot)ted(dot)byers(at)rogers(dot)com>, Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: php professional |
| Date: | 2007-02-22 23:43:25 |
| Message-ID: | B3731014-8AE3-4E6B-8AC9-462EBCD5BD74@event-s.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 22.02.2007, at 16:03, Ted Byers wrote:
> One of my problems with database development is how to construct
> analogously strong test cases in order to prove the code correct.
With tests you can't prove that your code is correct. You can only
show that your code works with the test cases. There are ways of
proving that code is correct, but I don't know anybody using that on
"real world code".
If you are using Java as a client you can use DbUnit for unit testing:
This can or cannot show that your latest changes didn't break stuff
that used to work ... ;-)
cug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2007-02-22 23:46:42 | Re: postgresql vs mysql |
| Previous Message | Joris Dobbelsteen | 2007-02-22 23:41:25 | Re: complex referential integrity constraints |