Just Code It Already

A couple days ago someone requested that we add a statment vs. row option into the create trigger screen for [http://phppgadmin.sourceforge.net phpPgAdmin], to which I responded that I was planning to add that in when I added in support for column based triggers once [http://archives.postgresql.org/pgsql-hackers/2005-03/msg00386.php Greg] was done with the patch. Of course it’s highly likely that we’ll want to release 3.6 of phpPgAdmin before Greg gets his patch done, so I left open the door that we could do the row/statement changes sooner if people wanted. This almost break out into an actual discussion about when we should code this but as I was writing up an excessivly long email (in retrospect it sure seemed excessivly long) in response to some questioning, I realized it was silly to debate this, since the changes were simple enough I could code it faster than I could convince anyone to wait for me to code it. So 3.6 will now have a row/statment options in create trigger which is really a better scheme than waiting; I’m not really sure why I was against it…. probably some left over tilting from my quickform/radio button experience.