Database Stub Not working Using Specmatic

[himanshuwadekar]

idproof.json
pincode1.json

I am encountering issues with two stubs in my project. Here are the details:

Stub 1: idproof.json
Issue: When working with idproof.json stub, I receive the following error:

Error in process method 'The database returned no natively generated identity value'.

Description: The table contains the primary key, which is also auto-incremented. However, despite this setup, the error persists.
Query: The query I'm using is:

@query("select deletionFlag from NonServicePincodeList n where n.pincode = ?1")

Stub 2: pincode1.json
Issue: When dealing with pincode1.json stub, I encounter the following error:

Error in process method 'For input string: "false"'.

Description: The error indicates a problem with the data format. The input string "false" is causing the issue.
Method: I'm using the following method:

uploadIdProofRepository.save(uploadIDProof);

I've verified the stubs, and they seem correct. However, they are not functioning as expected. Any assistance in resolving these issues would be greatly appreciated. Thank you.

[harikrishnan83]

@himanshuwadekar thanks for reaching out. I see two errors in the screenshots you have shared

• Query not stubbed - This happens if the query in the idproof.json is not matching the query fired from the application. Please review the logs to see if there is any data mismatch and set up your query stub JSONs to resolve this problem. I believe this is the same issue with your pincode.json also. Kindly check.
• The database returned no natively generated identity value - This is related to the hibernate annotations for the id column. I am able to reproduce the same error message by setting @GeneratedValue(strategy = GenerationType.IDENTITY) in our sample project. We will look into this and get back to you.

[harikrishnan83]

@himanshuwadekar About the The database returned no natively generated identity value that I mentioned above, the fix is now available as part of specmatic-jdbc release 0.11.2. Example:

For a table where the id is added as part of insert query the JSON would have looked as shown below.

{
  "query": "insert into product (cost,name,id) values (300,'Wooden Sofa',102)",
  "response": {
    "affectedRows": 1
  }
}

The same query for an auto-increment based table setup will be updated as follows. Please note how the response needs to contain the generated key for id column.

{
  "query": "insert into product (cost,name,id) values (300,'Wooden Sofa',default)",
  "response": {
    "affectedRows": 1,
    "generatedKeys": [
      {
        "id": 102
      }
    ]
  }
}