Geek asks and answers

Grails save () Does the domain object actually make a choice?

I am trying to take the JSONObject that I sent to my groovy controller. I can pass the object, see the JSON data, and then create a domain object from it. When I save it for writing to the database, it selects instead.

def save = {
    def input = request.JSON
    def instance = new Customers(input)
    instance.save()
}

here is my debug sql output

Hibernate: 
select
    this_.customers_id as customers1_237_0_,
    this_.customers_default_address_id as customers2_237_0_,
    this_.customers_dob as customers3_237_0_,
    this_.customers_email_address as customers4_237_0_,
    this_.customers_email_address2 as customers5_237_0_,
    this_.customers_fax as customers6_237_0_,
    this_.customers_firstname as customers7_237_0_,
    this_.customers_gender as customers8_237_0_,
    this_.customers_lastname as customers9_237_0_,
    this_.customers_membertype as customers10_237_0_,
    this_.customers_memo1 as customers11_237_0_,
    this_.customers_mname as customers12_237_0_,
    this_.customers_newsletter as customers13_237_0_,
    this_.customers_password as customers14_237_0_,
    this_.customers_point_date as customers15_237_0_,
    this_.customers_telephone as customers16_237_0_,
    this_.customers_total_points as customers17_237_0_,
    this_.customers_username as customers18_237_0_ 
from
    customers this_ 
where
    this_.customers_username=?

I don’t know what could have caused this.

+3
source share
2 answers

It looks like you have a unique username restriction. Grails makes the choice to check for uniqueness, since it is assumed that reading a single line is an easy task and it is preferable to run a unique constraint violation and exception.

.

+7

- :

Customers cust = new Customers(input);
println ("cust = "+cust);
cust.save();
0

More articles:


All Articles