Activity
From 10/21/2016 to 11/19/2016
11/16/2016
10/25/2016
- 10:31 AM Feature #1587: implement full support for word indexes
- Ovidiu Maxiniuc wrote:
> Indeed, this seems to be a conversion-time flaw. The string literal @"a"@ should not have b... - 10:26 AM Feature #1587: implement full support for word indexes
- Igor Skornyakov wrote:
> In fact the problem with case-sensitive expressions in the @WHERE@ clause is more general. ... - 08:12 AM Feature #1587: implement full support for word indexes
- In fact the problem with case-sensitive expressions in the @WHERE@ clause is more general. For example @for each tt n...
- 05:04 AM Feature #1587: implement full support for word indexes
- With 3197b rev. 11126 the issue with case-sensitivity of the @MATCHES@/@BEGINS@ arguments' is almost solved, The prob...
10/24/2016
- 08:34 AM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> Before we decide on an implementation for the word index updates (and deletions), we need to... - 08:31 AM Feature #1587: implement full support for word indexes
- Before we decide on an implementation for the word index updates (and deletions), we need to understand the way Progr...
- 07:40 AM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> OK, then it looks like we will take the approach in note 14.
Well, the only remaining quest... - 07:23 AM Feature #1587: implement full support for word indexes
- OK, then it looks like we will take the approach in note 14.
- 06:16 AM Feature #1587: implement full support for word indexes
- As far as I can see Hibernate Search is just a wrapper on the top of Apache Lucene. It keeps indexes in a separate st...
10/22/2016
- 04:06 AM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> Igor Skornyakov wrote:
> > Can an application logic use such dirty reads in any reliable an... - 09:54 PM Feature #1587: implement full support for word indexes
- Igor Skornyakov wrote:
> Can an application logic use such dirty reads in any reliable and consistent way? I can har...
10/21/2016
- 05:17 PM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> * What are the implications for dirty database? Progress does not use an MVCC model, so when... - 12:33 PM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> The documentation is clearly a good place to start, but ultimately, we need to confirm any d... - 12:29 PM Feature #1587: implement full support for word indexes
- Igor Skornyakov wrote:
> Eric Faulhaber wrote:
> > * How and when does Progress update its word break tables? We ne... - 12:00 PM Feature #1587: implement full support for word indexes
- Regarding the HQL compliance. As a hack it is possible to create auxiliary views for n = 1,..., N which are the "fibe...
- 11:26 AM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> * How and when does Progress update its word break tables? We need to match this behavior, s... - 10:44 AM Feature #1587: implement full support for word indexes
- Some other things to consider:
* How and when does Progress update its word break tables? We need to match this beha... - 09:55 AM Feature #1587: implement full support for word indexes
- We've already made several changes to the HQL->SQL generator in Hibernate. I could envision placing a marker keyword ...
- 09:37 AM Feature #1587: implement full support for word indexes
- Eric Faulhaber wrote:
> You have come up with some good potential solutions to deal with the CONTAINS syntax as SQL,... - 09:33 AM Feature #1587: implement full support for word indexes
- You have come up with some good potential solutions to deal with the CONTAINS syntax as SQL, but the impedance mismat...
- 05:03 AM Feature #1587: implement full support for word indexes
- The use of @UNION ALL@ can be avoided with use of CNF (Conjunctive Normal Form). For example
@SELECT <fields> FROM t...
Also available in: Atom