Re-encode DB password on connection failure
---
Key: CAY-801
URL: https://issues.apache.org/cayenne/browse/CAY-801
Project: Cayenne
Issue Type: Improvement
Components: Cayenne Core Library
Thanks. Must be something about forests and trees.
Thanks again,
Kevin
> -Original Message-
> From: Andrus Adamchik [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 12, 2007 1:41 AM
> To: dev@cayenne.apache.org
> Subject: Re: SoC code in SVN?
>
> Yeah, it's right here, off the main tru
[I am taking this to the list.]
Expressions (or SelectQueries for that matter) are most certainly NOT
going away. IMO they should be preserved along the lines of the
original design. Whether they are going to evolve to incorporate
features like outer joins is another question, and this depe
It was dealing with Oracle (and other Databases) requiring expressions
in this format:
(a <> ? or a is null)
instead of
(a <> ?)
I'm pretty sure that was the expression, but I can't remember the
details -- you were already aware of the problem at the time.
On 6/12/07, Andrus Adamchik <[EMAIL
Split expressions are going to be critical to implementing useful
outer joins. I'd say we need to do both or neither. My own
implementation of split expressions is very weak (I just hacked it
into the parser).
If I recall, the EJBQL equivalents were less flexible than the
combination of outer
Ok, got it. Yeah the DB would evaluate any condition that has a NULL
in it as FALSE. No objections to making Cayenne follow the Java
convention in that respect.
Andrus
On Jun 12, 2007, at 6:57 PM, Mike Kienenberger wrote:
It was dealing with Oracle (and other Databases) requiring expressio
There's no rush as far as the timing. I was asking mainly to see
whether we should close those Jiras. So from this discussion we
should leave them open.
Andrus
On Jun 12, 2007, at 7:04 PM, Mike Kienenberger wrote:
Split expressions are going to be critical to implementing useful
outer joi
Andrus,
I don't think this is quite the same thing.
Split expressions are probably part of the solution to this problem,
but not the entire solution. Nor did this feature have to be
implemented in order to have useful outer joins.
I'd recommend reverting your change to this Jira issue and ope
Andrus,
There are some unit tests for outer joins that I created while I was
doing my own patch.
Maybe these can be reused. I'm pretty sure they're included in the
outer join jira issue.
On 6/12/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
We had extensive discussions with Mike K. on advanc
Sorry, I probably misunderstood your previous explanation:
"Split expressions are going to be critical to implementing
useful outer joins."
The changes I've made to CAY-514 are undone. What I was trying to do
(but probably did it wrong) is to categorize Jira's according to the
main con
Split Expressions
-
Key: CAY-802
URL: https://issues.apache.org/cayenne/browse/CAY-802
Project: Cayenne
Issue Type: New Feature
Components: Cayenne Core Library
Reporter: Mike Kienenberger
As
EJBQL Parameters support
Key: CAY-803
URL: https://issues.apache.org/cayenne/browse/CAY-803
Project: Cayenne
Issue Type: Task
Components: Cayenne Core Library, Cayenne JPA
Affects Versions: 3.0
12 matches
Mail list logo
