In-correct if-clause in the code-base about compoships HOT 6 CLOSED

@mdemblani Thanks for reporting this issue. Can you please provide more details (some code example with the resulting query)?

from compoships.

About to close this... please reopen if you have more details

from compoships.

Hi,

Regarding the issue, consider the following case, there is a relation between 2 models, says

• Model A
• Model B

The models are related as follows: Model B belongsTo Model A on two keys : X and Y, which are both of type integer. The foreign key constraints are managed on the application level, and not on the DB(there was a reason to do this).

The relation foreign keys start as follows: for X they start from 1 and for Y they start from 0.
The relation had to start with 0, due to the underlying requirements which results in the following case:

In my final query, just with the foreign keys, I have 2 foreign keys(X and Y) as defined by my relation but only a single binding (for X). The binding for Y is not considered, since the check on Line 25 performs a check on whether the value is a boolean true and not whether the value is set or put up a default value of null. This results in an error, in the form of a wrong query being generated.

from compoships.

@mdemblani Thanks for the details. I pushed a fix to the master branch. You may test it and give me feedback.

from compoships.

Fixed in 1.1.3

from compoships.

Thanks. I'll check it out.

from compoships.