If you're using J, you are probably doing analytics and stats. That means you are looking for patterns in a handful of attributes across a large population - i.e. columnar.
As others have said, row-based makes sense for most OLTP / app databases. You're probably not writing those products in J.
As others have said, row-based makes sense for most OLTP / app databases. You're probably not writing those products in J.