org.postgresql.util.PSQLException: No value specified for parameter 1 upon user.save()

can you please attach an example that reproduces the problem, or at least the SQL that is causing the issue from the logs

I've investigated further and found out that the error stems from validation ( validate(), as opposed to save() ) as the following fails with the mentioned error:

User user = User.findByConfirmationToken('bc73701c-d280-4de0-8951-7af9f2a3d636')
user.validate()

Here's the according Hibernate debug output:

Hibernate: select this_.id as id7_0_, this_.version as version7_0_, this_.account_expired as account3_7_0_, ... from "user" this_ where this_.email=?
Hibernate: select this_.id as id7_0_, this_.version as version7_0_, this_.account_expired as account3_7_0_, ... from "user" this_ where this_.username=?
Hibernate: select this_.id as id7_0_, this_.version as version7_0_, this_.account_expired as account3_7_0_, ... from "user" this_ where this_.username ilike ? and this_.id<>?
Hibernate: select this_.id as id7_0_, this_.version as version7_0_, this_.account_expired as account3_7_0_, ... from "user" this_ where this_.id=?
["http-bio-8080"-exec-3] 10-03 11:58:06 229 ERROR org.hibernate.util.JDBCExceptionReporter | Für den Parameter 1 wurde kein Wert angegeben.

I've now also tested with more stable versions:

• Grails 2 revision #1468
• PostgreSQL 8.4.8 and 9.1.0
• JDBC: postgresql:postgresql:8.4-702.jdbc4

The result is always the same.

(I am having trouble to output the SQL with actual data - tried 'logSql' in DataSource.groovy and trace 'org.hibernate.sql', 'org.hibernate.type' in log4j (Config.groovy) )

I was able to track down the problem and strip it down to a minimum. Attached is a grails app that allows to reproduce the problem (g8101.tar.bz2). The relevant parts are:

class User {
	static hasOne	= [ acceptedInvitation: Mapping ]
	static mappedBy	= [ acceptedInvitation: 'invitee' ]

	// ...
	static constraints = {
		// THE EVIL:
		acceptedInvitation	nullable: true, unique: true
	}
	// ...
}

class Mapping {
	static belongsTo = [invitee:User]
	User issuer
}

I am unaware about the actual internals, but the user.validate() seems to 'forget' to send the value (parameter #1) when checking fur uniqueness on `acceptedInvitation`. Maybe someone could explain what is actually going on here?

Removing the unique-contraint (and placing in into the Mapping DC, if desired), resolves the issue.

I wonder if the nullable-constraint is okay here

By the way: The problem also occurs when H2 is used as a database (probably it's DB-independent in the first place ...).

As I've been spending 10 hours on this topic, I'd like to ask if you could implement a noticable and understandable error message for such cases?

See also: http://stackoverflow.com/questions/7220006/grails-hibernate-does-select-before-insert-without-passing-id-argument-value

I'm getting this as well, Graeme. Under nearly identical conditions. I've also seen online hints that there was an old bug in Hibernate that could cause this, owing to a faulty optimization in PreparedStatement.

Perhaps time to update to Hibernate 3.6.10? Or 4.1.x? Please advise.

Sorry, I meant to add that I'm seeing this using MySQL, so it's definitely not PSQL-specific.

See this Stackoverflow discussion:

http://stackoverflow.com/questions/7290563/hibernate-exception-no-value-specified-for-parameter-2-when-running-grails-1-3

Further confirmation: I found a domain class where I had unknowingly used the "unique: true, nullable: true" combination. As soon as I removed the uniqueness constraint, voila, all is working.

For the record Eli Israel's error seems a different problem to the original issue

We get the exact same thing on H2 when using hasOne and unique:true.

Burt - could you look at this one please