Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Fri, 20 Jul 2007 17:28:39 +0200
From: Dag.Wanvik@Sun.COM (Dag H. Wanvik)
Subject: Re: [jira] Assigned: (DERBY-2925) Prevent export from overwriting
 existing files
In-reply-to: <469BEE25.6040906@sbcglobal.net>
Sender: Dag.Wanvik@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x1oxk5sv3xi0.fsf@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <15385046.1184285525014.JavaMail.jira@brutus>
 <x1oxfy3oo6no.fsf@sun.com> <469BEE25.6040906@sbcglobal.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.0.50 (usg-unix-v)

Kathey Marsden <kmarsdenderby@sbcglobal.net> writes:

> I don't think adding another jar will improve usability.  I think the
> restriction of a dedicated export directory or restrictions on
> directory names for export will also not improve usability.   I think
> it is reasonable to expect the user to delete pre-existing files
> before exporting over them.  But this is all just a straight
> difference of opinion.

Just want to state that my comment to this issue would not cause me to
vote -1 for the issue or the release :)

But looking at how DERBY-2436 is also open (misuse of IMPORT to read
aunauthorized data); I guess i feel that some more general way of
limiting *which* files are read/written by export/import is the way to
go, even if it risks causing some incompatibility.

Thanks,
Dag