Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D8E6410E78 for ; Thu, 16 Jan 2014 19:44:45 +0000 (UTC) Received: (qmail 69606 invoked by uid 500); 16 Jan 2014 19:44:45 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 69490 invoked by uid 500); 16 Jan 2014 19:44:44 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 69467 invoked by uid 99); 16 Jan 2014 19:44:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jan 2014 19:44:43 +0000 X-ASF-Spam-Status: No, hits=0.1 required=5.0 tests=FSL_NEW_HELO_USER,HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Dyre.Tjeldvoll@oracle.com designates 156.151.31.81 as permitted sender) Received: from [156.151.31.81] (HELO userp1040.oracle.com) (156.151.31.81) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jan 2014 19:44:30 +0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s0GJi7Pb015525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Jan 2014 19:44:08 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s0GJi6lN028857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 16 Jan 2014 19:44:07 GMT Received: from abhmp0003.oracle.com (abhmp0003.oracle.com [141.146.116.9]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s0GJi6gK018694 for ; Thu, 16 Jan 2014 19:44:06 GMT Received: from [192.168.0.100] (/84.202.202.148) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 16 Jan 2014 11:44:06 -0800 From: Dyre Tjeldvoll Content-Type: multipart/alternative; boundary="Apple-Mail=_4159B2F8-EE19-4C74-AD65-8F5BCDBE2107" Message-Id: <7D89B1DB-9500-463D-ABA5-AF09217FB0F1@oracle.com> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Derby in production environment Date: Thu, 16 Jan 2014 20:44:09 +0100 References: <1389883309360-136557.post@n7.nabble.com> <408BCA9D-455E-4BD3-8139-B86DAEEC258A@oracle.com> To: Derby Discussion In-Reply-To: <408BCA9D-455E-4BD3-8139-B86DAEEC258A@oracle.com> X-Mailer: Apple Mail (2.1827) X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_4159B2F8-EE19-4C74-AD65-8F5BCDBE2107 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16. jan. 2014, at 15:56, Dyre Tjeldvoll = wrote: > The URL you are referring to is NOT the official Derby web page, and = the statements made there are not correct for the latest version of = Apache Derby. The official page can be found here >=20 > http://db.apache.org/derby/ >=20 > Derby *is* used in production and it has security controls as = described here: >=20 > Configuring security for Derby >=20 > I *think* that the page you refer to describe the state of a = MessageBroker application running in WebSphere that *can* use Derby = internally, but this configuration is not recommended for the reasons = you mention. To be clear: The statement is misleading in that it makes it sound as if = Derby does not have security controls or an optimizer. In fact Derby has = both, but I believe the article is trying to say that the Message Broker = application does not configure the controls for Derby and they have not = tuned their queries for Derby. Regards, Dyre >=20 > Regards, >=20 > Dyre >=20 > On 16. jan. 2014, at 15:41, AirDT wrote: >=20 >> Hello,=20 >>=20 >> I want to use Derby in a production environment and I read the = following >> sentence:=20 >> "The Derby database Has No Associated security controls, and no >> optimizations-have-been performed. Reasons For thesis, do not use = Derby in a >> Production environment."=20 >> in doc=20 >> = http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=3D= %2Fcom.ibm.etools.mft.doc%2Fah35004_.htm >>=20 >> Is Derby currently being used successfully in production = environments? >>=20 >> Any information would be appreciated. Thanks in advance. >>=20 >> AirDT >>=20 >>=20 >>=20 >> -- >> View this message in context: = http://apache-database.10148.n7.nabble.com/Derby-in-production-environment= -tp136557.html >> Sent from the Apache Derby Users mailing list archive at Nabble.com. >=20 --Apple-Mail=_4159B2F8-EE19-4C74-AD65-8F5BCDBE2107 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On 16. jan. 2014, at 15:56, Dyre = Tjeldvoll <Dyre.Tjeldvoll@oracle.com>= ; wrote:

The = URL you are referring to is NOT the official Derby web page, and the = statements made there are not correct for the latest version of Apache = Derby. The official page can be found here

=

 Derby *is* used in production and it has = security controls as described here:


I *think* that the page you refer to = describe the state of a MessageBroker application running in WebSphere = that *can* use Derby internally, but this configuration is not = recommended for the reasons you = mention.

To be clear: The = statement is misleading in that it makes it sound as if Derby does not = have security controls or an optimizer. In fact Derby has both, but I = believe the article is trying to say that the Message Broker application = does not configure the controls for Derby and they have not tuned their = queries for = Derby.


Regards,

Dyre


Regards,

= Dyre

On 16. jan. 2014, at 15:41, AirDT <contact@solgt.fr> = wrote:

Hello,

I want to use Derby in a production = environment and I read the following
sentence:
"The Derby = database Has No Associated security controls, and = no
optimizations-have-been performed. Reasons For thesis, do not use = Derby in a
Production environment."
in doc
http://publib.boulder.ib= m.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=3D%2Fcom.ibm.etools.mft.do= c%2Fah35004_.htm

Is Derby currently being used successfully = in production environments?

Any information would be appreciated. = Thanks in advance.

AirDT



--
View this message = in context: http://apache-database.10148.n7.nabble.com/Derby-i= n-production-environment-tp136557.html
Sent from the Apache Derby = Users mailing list archive at Nabble.com.


= --Apple-Mail=_4159B2F8-EE19-4C74-AD65-8F5BCDBE2107--