Joshua D. Drake wrote:
This brings me here. I have heard of PostGreSQL, so it’s not new to me.
But all this licensing is. And maybe you can help get some clarification
for the MySQL licensing too.
You can do anything you want with PostgreSQL. You can close source it,
you can sell it, you can rename it.
You just can't sue us if something goes wrong.
LOL!!!!!
No charge.
Sincerely,
Joshua D. Drake
We will not be selling the database software. We may install it for
them, though. In fact, most of the time, we will be the ones to install
it, and we charge for that time. Our customers are very aware that we
did not write it, nor are we selling it. Even if they are to purchase
SQL Server, they are the ones to purchase it directly, not us. We
purchase the connectivity kits that we use to connect to the database,
and then pass that cost on to the customer. It is purchased in their
name with their information. We do not charge extra or tack on any fees.
We do it this way so that no screw ups are made… The connectivity kit is
the one that connects to the database; we connect to the connectivity
kit through our software.
Knowing all this, what do we need to purchase, what can we do and what
can’t we do? It’s hard getting a straight answer from anyone that is why
I am here. If we can’t do it, we won’t. If we can save our customers
some money while getting them really good options and software, we would
like to do that. But on the same token, we don’t to do anything unfair
or illegal.
Thank you for your time.
Aaron
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
