Validaiton on transactions

[Rodrigo Araujo]

Hey guys,

I need some help here to clarify how I'm supposed to do this:

I have two models: Files and Courses. Files belongs to Course and has a CourseId field. At some point I needed to use transactions to validate both of them before inserting them, however, one of my validation rules for the File model verifies if the informed CourseId exists (it's useful in other cases where I don't use transactions) and this rule is flagged during the transaction because there's no CouseId during it, as we can all expect.

I think this could be fixed if I could dinamically disable the validation rule for the CourseId field, but apparently this is not possible yet. Another approach would be virtual fields, but this one is not quite "elegant".

How can I solve this?

Thanks!

[Mark Lester]

if this is a db level condition on a foreign key then no, you arent just going to able to drop it for a specific transaction i would think.
if it is a validation rule specced by you then you could pass a value in options to turn it off.

[Mick Hansen]

Depending on the RDBMS it's possible in some cases to defer foreign key checks in a transaction.

--

Mick Hansen

@mhansendev
mhansen.io

[Rodrigo Araujo]

I manually created the validation rule, however I don't see in the docs how I can disable the validation in one field, at least not in ".create()". Apparently I can do that using the option "skip" on ".validate()". Do you know how can I do that?

Thanks

[Rodrigo Araujo]

Actually it works, my bad. I'm using "skip".  Thank you guys!