I would like to just take a moment to express my love for Spring JDBC. I just deleted giant swaths of database connection handling code from an app I’m maintaining by replacing a DAO with a Spring JDBC version. If you haven’t taken the time to learn about it, check it out here.
Monthly Archives: January 2010
Moving code from one SVN to another
I am currently working on merging some of the projects from two different SVN repositories to one repository. I don’t want to do a full dump of one and restore to the other, because the organization is a bit different in each. The solution is something like this:
- Dump the entire source repository
- Use svndumpfilter to split the dump into separate files
- Import each file separately into the right spot in the target repository
Here’s a couple one-liners to split the dump file (I love Unix):
$ cat source_repo.dump |grep -a ^Node-path: | grep -v / |uniq | sed “s/Node-path: //g” > projectlist.txt
$ for i in `cat projectlist.txt`; do cat svn_oasis.dump | svndumpfilter include $i > $i.dump; done
The first command creates a list of top level directories, and the second does the splitting. Now, you have a separate dump file for each different top level directory in the source repo. This can be tweaked if you want to split it based on different criteria.
Once you have the dump file for a project and you want to import it, you use a command like this:
cat project.dump | svnadmin load /usr/local/svn/myrepo
Make sure that the path you are importing doesn’t exist. I did not make sure, then I think svnadmin imported a bunch of stuff, but was unable to create the top level dir, so it probably left a bunch of orphaned crap in the repo. The load process seems pretty half baked, so be careful 🙂
PHP
Samson pointed out this PHP bug report to me:
http://bugs.php.net/bug.php?id=50696
It is an entertaining read. This illustrates a couple of problems with PHP that make me wary of using it for anything too serious. They seem to have a flagrant disregard for specification of their API, as well as backward compatibility. Additionally, the lack of strong typing appears to be the source of all of their issues. I’m not going to say weak typing is bad, I just find strong typing forces the programmer to resolve issues at compile time instead of at runtime (i.e. before the end user is actually running the code and the app blows up on them).
All of this culminates into this bug report, which erupts into a flame war, uncovering the underlying big egos that have probably led to the feeling that strict specification is unnecessary and developers can just “deal with” changes in the API in minor releases. Both of the PHP developers involved in the conversation were extremely unprofessional and resorted to such tactics as name dropping to argue their case.
It sucks, because I think PHP would be pretty nice if they were just a little more strict and professional about these things (both the technical and personal issues).
X Windows
Recently, I have heard several references to the term “X Windows”. For all of you uninformed fools out there, here’s the official word straight from the horse’s mouth (see man X):
The X.Org Foundation requests that the following names be used when referring to this software:
X
X Window System
X Version 11
X Window System, Version 11
X11
So, as you can see, there is no reference to “X Windows”. It has nothing to do with “Windows”, so don’t call it that.