幽默我:Postgresql vs. MySql(特别是许可) [英] Humor me: Postgresql vs. MySql (esp. licensing)

查看:93
本文介绍了幽默我:Postgresql vs. MySql(特别是许可)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是的,我知道您之前已经看过上述主题了,所以请温柔地跟着火焰喷射器。


我准备了与我的公司管理层讨论

关于作为MySql商店或Postgresql商店的进展。


我认为我们是应该使用PG,因为完整的ACID

支持,以及涉及的许可证。我公司聘请的顾问

带我进去,正在努力推动MySql,引用速度和社区

支持,以及ACID支持。

我对MySQL的最大担忧是许可。我们需要保持低成本,

,最后我记得母公司对公平

使用非常严格。根据GPL。如果我记得的话,他们甚至说如果公司只是在公司内部使用,那么公司就必须获得商业版的许可。


另外,我认为Postgresql在速度类别中使用MySql几乎赶上了
...是不是这样?


最后,mysql中的ACID支持似乎总是很糟糕....也许

这已经改变了吗?


感谢任何输入(武器装备) ;)你可以提供。


John


------------------ ---------(广播结束)---------------------------

提示3:如果通过Usenet发布/阅读,请发送适当的

subscribe-nomail命令到 ma ** *****@postgresql.org 这样你的

消息可以干净地通过邮件列表

解决方案

2003年10月8日星期三11:28:00 -0400(美国东部时间)约翰Wells< jb@sourceillustrated.com>写道:

我认为我们应该使用PG,因为完整的ACID
支持和涉及的许可证。我的公司雇用的顾问在带给我之前正在努力推动MySql,引用速度和社区支持以及ACID支持。




你还应该引用符合标准。在许多方面,MySQL与SQL标准有很大的不同.b $ b。并不是说完全符合要求,但有些地方认为MySQL非常在那里。


richard

-

Richard Welty rw****@averillpark.net

Averill Park Networking 518-573-7592

Java,PHP,PostgreSQL,Unix,Linux,IP网络工程,安全性

------ ---------------------(广播结束)------------------------ ---

提示6:您是否搜索了我们的列表档案?

http://archives.postgresql.org


2003年3月8日星期三,16:28,约翰威尔斯写道:

是的,我知道你以前看过上面的主题,所以请温柔地跟着火焰喷射器。

我是准备进入讨论w关于我作为MySql商店或Postgresql商店的管理,我公司的管理层。

我认为我们应该使用PG,因为完整的ACID
支持,以及涉及的许可证。我公司聘请的一位顾问在带给我之前,正在努力推动MySql,引用速度和社区支持,以及ACID支持。


速度取决于使用的性质和查询的复杂程度。如果你正在更新相关表格,那么ACID至关重要,而且...... b $ b MySQL没有提供它。

我最关心的问题与MySQL是许可。我们需要保持低成本,最后我记得母公司对公平使用的要求非常严格。根据GPL。如果我记得,他们甚至说如果公司只是在公司内部使用,那么他们就必须获得商业版的许可。


除非他们实际为GPL附加额外条件(即此

产品根据GPL许可,但有以下额外条件......)

这是垃圾。 GPL允许您在内部使用

软件执行您喜欢的操作;它的限制仅适用于进一步的分配。 MySQL会像你一样支付你的支持或购买一个商业许可证,但你只需要购买一个许可证,如果你想要b $ b分发修改或链接的MySQL而不分发你自己的

源代码。


如果该位置发生变化,我们(Debian)将需要从

Debian'移动MySQL它的非自由部分的主存档,甚至完全放弃了它的b $ b。所以,如果有必要,请告诉我!

另外,我的印象是Postgresql在速度类别中与MySql相当多了......是不是这样的?


MySQL对于简单查询非常有用,一次不会有太多用户。

否则它不比PostgreSQL好,而且往往更糟糕无法使用,

根据我见过的其他帖子。

最后,mysql中的ACID支持似乎总是一种黑客......也许
这有改变了吗?


不是我所知道的。

感谢您提供的任何输入(武器;))。



我接管了用MySQL编写的项目的维护。这总是一场噩梦。没有触发器,外键或约束,以及奇怪的

时间戳处理。如果有这个选择,我就不会用10美元b $ b足杆触摸它。


-

Oliver Elphick < a href =mailto:Ol ************ @ lfix.co.uk> Ol ************ @ lfix.co.uk

英国怀特岛 http://www.lfix .co.uk / oliver

GPG:1024D / 3E1D0C1C:CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C

======== ================================

当他受到诱惑时,不要让任何人说出来,我很想受到上帝的伤害。因为上帝不能受到邪恶的诱惑,也不能诱惑任何人;但每个男人都受到诱惑,当他因为他自己的欲望被吸引而被诱惑时。

詹姆斯1:13,14

---------------------------(广播结束)----------------- ----------

提示7:别忘了增加你的免费空间地图设置


< blockquote> Richard Welty写道:

2003年10月8日星期三11:28:00 -0400(美国东部时间)John Wells< jb@sourceillustrated.com>写道:

我认为我们应该使用PG,因为完整的ACID
支持和涉及的许可证。我的公司雇用的顾问在带给我之前正在努力推动MySql,引用速度和社区支持以及ACID支持。



你还应该引用符合标准。在许多方面,MySQL与SQL标准有很大不同。并非完全符合要求,但有些地方MySQL严重在那里。




是的...就像插入biiig号码一样交易中的整数字段没有

错误,并且在提交后没有收回..或接受''00 -00-00 00:00:00''

a有效日期时间戳...类似的东西..


与ACID的偏差是多少? 180度...... :-)


我的一个朋友昨天用mysql丢失了数据..机器被取下了

磁盘升级和mysql显然没有提交最后一个插入..好吧他是

使用myisam但仍然.. :-)


Shridhar

- --------------------------(广播结束)------------------- --------

提示3:如果通过Usenet发布/阅读,请发送适当的

subscribe-nomail命令给 ma ******* @ postgresql.org ,以便您的

消息可以干净地通过邮件列表


Yes, I know you''ve seen the above subject before, so please be gentle with
the flamethrowers.

I''m preparing to enter a discussion with management at my company
regarding going forward as either a MySql shop or a Postgresql shop.

It''s my opinion that we should be using PG, because of the full ACID
support, and the license involved. A consultant my company hired before
bringing me in is pushing hard for MySql, citing speed and community
support, as well as ACID support.

My biggest concern with MySQL is licensing. We need to keep costs low,
and last I remember the parent company was being pretty strict on "fair
use" under the GPL. If I recall, they even said a company would have to
license the commercial version if it were simply used operationally within
the company.

Also, I was under the impression that Postgresql had pretty much caught up
with MySql in the speed category...is this not the case?

Finally, ACID support in mysql always seemed kind of a hack....perhaps
this has changed?

Thanks for any input (armament ;) ) you can provide.

John

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

解决方案

On Wed, 8 Oct 2003 11:28:00 -0400 (EDT) John Wells <jb@sourceillustrated.com> wrote:

It''s my opinion that we should be using PG, because of the full ACID
support, and the license involved. A consultant my company hired before
bringing me in is pushing hard for MySql, citing speed and community
support, as well as ACID support.



you should also cite conformity to standards. MySQL is significantly
different from SQL standards in a number of regards. not that any are fully
conformant, but there are spots where MySQL is seriously "out there".

richard
--
Richard Welty rw****@averillpark.net
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org


On Wed, 2003-10-08 at 16:28, John Wells wrote:

Yes, I know you''ve seen the above subject before, so please be gentle with
the flamethrowers.

I''m preparing to enter a discussion with management at my company
regarding going forward as either a MySql shop or a Postgresql shop.

It''s my opinion that we should be using PG, because of the full ACID
support, and the license involved. A consultant my company hired before
bringing me in is pushing hard for MySql, citing speed and community
support, as well as ACID support.
Speed depends on the nature of use and the complexity of queries. If
you are doing updates of related tables, ACID is of vital importance and
MySQL doesn''t provide it.
My biggest concern with MySQL is licensing. We need to keep costs low,
and last I remember the parent company was being pretty strict on "fair
use" under the GPL. If I recall, they even said a company would have to
license the commercial version if it were simply used operationally within
the company.
Unless they actually attach extra conditions to the GPL (i.e. "This
product is licensed under GPL with the following extra conditions...")
this is rubbish. The GPL allows you to do what you like with the
software internally; its restrictions only apply to further
distribution. MySQL would _like_ you to pay for support or buy a
commercial licence, but you only _need_ to buy a licence if you want to
distribute a modified or linked MySQL without distributing your own
source code.

If that position changes, we (Debian) will need to move MySQL from
Debian''s main archive to its non-free section, or even drop it
altogether. So do let me know if that becomes necessary!
Also, I was under the impression that Postgresql had pretty much caught up
with MySql in the speed category...is this not the case?
MySQL is very good for simple queries by not too many users at a time.
Otherwise it''s no better than PostgreSQL and often worse to unusable,
according to other posts I''ve seen.
Finally, ACID support in mysql always seemed kind of a hack....perhaps
this has changed?
Not that I know of.
Thanks for any input (armament ;) ) you can provide.



I took over maintenance of a project written in MySQL. It is a total
nightmare. No triggers, foreign keys or constraints, and bizarre
timestamp handling. Given the choice, I wouldn''t touch it with a ten
foot pole.

--
Oliver Elphick Ol************@lfix.co.uk
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"Let no man say when he is tempted, I am tempted of
God; for God cannot be tempted with evil, neither
tempteth he any man; But every man is tempted, when he
is drawn away of his own lust, and enticed."
James 1:13,14
---------------------------(end of broadcast)---------------------------
TIP 7: don''t forget to increase your free space map settings


Richard Welty wrote:

On Wed, 8 Oct 2003 11:28:00 -0400 (EDT) John Wells <jb@sourceillustrated.com> wrote:

It''s my opinion that we should be using PG, because of the full ACID
support, and the license involved. A consultant my company hired before
bringing me in is pushing hard for MySql, citing speed and community
support, as well as ACID support.


you should also cite conformity to standards. MySQL is significantly
different from SQL standards in a number of regards. not that any are fully
conformant, but there are spots where MySQL is seriously "out there".



Yeah.. like inserting a biiig number in integer field in a transaction without
error and not getting it back after commit.. or accepting ''00-00-00 00:00:00'' as
a valid datetime stamp.. something like that..

How much deviation is that from ACID? 180 degrees...:-)

One of my friend lost data with mysql yesterday.. The machine was taken down for
disk upgrade and mysql apperantly did not commit the last insert.. OK he was
using myisam but still..:-)

Shridhar
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly


这篇关于幽默我:Postgresql vs. MySql(特别是许可)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆