FWD » Core Development » Database

11/16/2016

01:11 PM Bug #1914 (Closed): database conversion requires Internet connectivity

Greg Shah

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... Igor Skornyakov

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. ... Ovidiu Maxiniuc

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... Igor Skornyakov

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... Igor Skornyakov

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... Igor Skornyakov

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... Eric Faulhaber

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... Igor Skornyakov

07:23 AM Feature #1587: implement full support for word indexes

OK, then it looks like we will take the approach in note 14. Eric Faulhaber

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... Igor Skornyakov

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... Igor Skornyakov

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... Eric Faulhaber

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... Igor Skornyakov

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... Igor Skornyakov

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... Eric Faulhaber

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... Igor Skornyakov

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... Igor Skornyakov

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... Eric Faulhaber

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 ... Eric Faulhaber

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,... Igor Skornyakov

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... Eric Faulhaber

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... Igor Skornyakov

10/20/2016

03:38 PM Feature #1587: implement full support for word indexes

I like the directness of this approach and in fact I have been trying to move as much HQL processing to SQL for perfo... Eric Faulhaber

02:40 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Of course, we want as few round trips to the database as possible, ideally only one. Please ... Igor Skornyakov

02:24 PM Feature #1587: implement full support for word indexes

Of course, we want as few round trips to the database as possible, ideally only one. Please provide an example of wha... Eric Faulhaber

01:47 PM Feature #1587: implement full support for word indexes

Regarding the queries with use of a word-break table. In a case of the complex expression in the @CONTAINS@ it can be... Igor Skornyakov

07:28 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> Here is the (expanded) summary of the recent e-mail discussion between Greg, Eric, Ovidiu a... Igor Skornyakov

06:30 AM Feature #1587: implement full support for word indexes

Here is the (expanded) summary of the recent e-mail discussion between Greg, Eric, Ovidiu and myself regrading the su... Igor Skornyakov