Jason Wells

chrisbowler: This made me laugh, but I was surprised by the...

Fri, 12 Nov 2010 12:44:38 -0700

chrisbowler:

This made me laugh, but I was surprised by the salary differences.

[ via @behoff ]

"Friends should be simple and deep, not complex and superficial."

Sun, 12 Sep 2010 14:02:01 -0600

“Friends should be simple and deep, not complex and superficial.”

- Mr. Rogers

A Lesser Photographer: The Photo Bubble

Mon, 05 Jul 2010 12:09:15 -0600

A Lesser Photographer: The Photo Bubble:

Bubbles are usually reserved for complex products that most regular people own, and, now, more and more regular people are carrying powerful cameras (their phones) in their pockets wherever they go. The thing I’ve noticed is that they’re doing so without regard to the specs. They want a good picture (a result). That’s it. They exist comfortably outside the bubble, almost unaware the bubble exists.

I couldn’t agree more. Tech blogs and news sites however, are increasingly living inside these bubbles. I have made a concerted effort as of late to move myself out of these bubbles and into a world where I have essential tools that perform well.

Update: Here are two places, other than A Lesser Photographer, that have helped to inspire me in that direction recently:

Minimal Mac

Chris Bowler

"You can spend tons on fancy equipment, but if you’ve got nothing to say…well, you’ve got nothing to..."

Wed, 12 May 2010 20:08:39 -0600

“You can spend tons on fancy equipment, but if you’ve got nothing to say…well, you’ve got nothing to say.”

- REWORK (via alesserphotographer)

"So much complexity in software comes from trying to make one thing do two things."

Fri, 07 May 2010 16:34:00 -0600

“So much complexity in software comes from trying to make one thing do two things.”

- Insight by Ryan at 37signals (via minimalmac)
Echos the same sentiments as 37signals’ book Rework. An excellent read I just finished. I highly recommend it.

Hibernate OneToMany Annotations

Wed, 15 Jul 2009 20:34:00 -0600

As it was hard for me to find a clear example of a OneToMany join using Hibernate annotations in Java the other day, I decided to write this up.

This is an example of a unidirectional OneToMany join in Java using Hibernate. The JoinColumn name is a foreign key in the Message table. This will allow access to the Set of the messages that have been sent to the particular user. It automatically joins on the primary key of the User table.

@Entity

@Table(name = "user")

public class User {

    @Id

    @GeneratedValue

    private Integer user_id;

    private String first_name;

    private String last_name;

    private String user_name;



    @OneToMany(cascade = CascadeType.ALL)

    @JoinColumn(name="to_user")

    private Set<Message> messagesTo;

}

This is the Message class that corresponds with the User class. The join is on the to_user column which is shown using a column annotation to specify a different name in the database. The join however will give a set of complete Message objects and not just the column joined.

@Entity

@Table(name = "message")

public class Message {

    @Id

    @GeneratedValue

    private Integer message_id;

    @Column(name = "from_user")

    private Integer from;

    @Column(name = "to_user")

    private Integer to;

    @Column(name = "message_text")

    private String message;

    @Column(name = "date_sent")

    private Date date;

}

With this join you can name use a generic getMessagesTo() function that would allow you to easily retrieve the Set of all the messages sent to a particular user. The process can be easily repeated to retrieve the messages sent from a user as well.

It is important to note that this join is a unidirectional relationship. It does not provide for retrieving a User from an instance of Message.