The first category, yes. The second: it depends on your license conditions.
A common misconception.
In all the licensing fetishes on the net very few people realise their true legal status - or lack of.
You would be suprised at how many licences are mostly invalid.
Your other points have validity too. but these things are seldom as simple as originally suggested is what
I was trying to get across - and it bothers me that people fairly new to the field could be put off
their best approach.
There are far too many computing decisions being made based on clever marketing and ignorance.
So who is at fault in the case of MySQL support in Lazarus.
It is not an issue of "fault" It is a case of what is a claimed capability. If you claim mySQL then you are obligated
to provide blanket mySQL. If you want to limit that to a specific subset - you just say that.
In the case of FPC/Lazarus - there is no issue I know of. The latest client is now supported. Presumably
so will the next. If not - then those of us using mySQL will stop using lazarus and go elsewhere.
I will repeat because there seems to be confusion and the point is key: It is NOT the job of developers to tell users what to use. It is the job of developers to fulfill the needs of users.
I suggested a poll of dbase lazarus users because I thought that would be the most useful here.
I stand by my previous comments as a response.