Hi Abel,

Thanks for the feedback.
Don't worry about it!

Cheers
Lukas

2012/4/16 Abel Birya <[email protected]>:
> Hey Lukas,
>
> My laptop is still having issues. If it is ok with you go ahead and do the
> implementation  of the insert ignore functionality. I hope in future I can
> be able to contribute towards the project.
>
> Kind regards.
>
> Abel
>
> ________________________________
> From: "Lukas Eder" <[email protected]>
> To: [email protected]
> Sent: Monday, April 16, 2012 11:25:28 AM
>
> Subject: Re: JOOQ INSERT IGNORE
>
>> I don't think you need to propagate warnings. In most cases they can be
>> ignored. They are not converted into exceptions by database engine and in
>> those rare cases when user wants them, he can call getWarnings() to check
>> if
>> there are any warnings.
>
> That's a good hint. This option should be mentioned in the Javadoc of
> the relevant methods, also in the loader API:
> https://sourceforge.net/apps/trac/jooq/ticket/1320
>
>> If I were a developer of Java database
>> classes, I would introduce an option to throw warnings as exceptions. I
>> like
>> clean code. I don't want even warnings to be there as a result of query
>> execution.
>
> Yes, that would be nice. Under the hood, JDBC probably allows for
> this, as java.sql.SQLWarning extends SQLException...
>
> Cheers
> Lukas
>

Reply via email to