FWD » Core Development » Database

02/23/2021

06:34 PM Bug #5056: Temp-tables and unique indexes

Similar to the patch proposed in #4884-15, I have fixed the cases identified above. The three main xfer testcases are... Ovidiu Maxiniuc

07:43 PM Bug #5056: Temp-tables and unique indexes

I found the cause for the 'regression' of your patch. It is probably not a single thing, but a couple of issues which... Ovidiu Maxiniuc

02/20/2021

11:26 AM Feature #1587: implement full support for word indexes

Finished with word tables support for denormalized extent fields. Tested with a large customer app. and with test app... Igor Skornyakov

07:46 PM Bug #5056: Temp-tables and unique indexes

I used your patch to run the xfer tests and things have changed. It is not perfect, but I cannot tell exactly why.
... Ovidiu Maxiniuc

02/19/2021

11:31 AM Feature #1587: implement full support for word indexes

Added word tables' support for custom extents (conversion and database import).
Committed to 3821c/12031 Igor Skornyakov

10:48 AM Feature #4397 (Closed): add database attrs, methods and options

Ovidiu has recently confirmed that testing passed for the features in this task. Greg Shah

02/18/2021

06:27 PM Bug #5056: Temp-tables and unique indexes

Eric,
I looked deeper into the server's log (there are a lot of @java.lang.IllegalStateException: Empty scopes in Un... Ovidiu Maxiniuc

06:19 PM Bug #5056: Temp-tables and unique indexes

Eric,
I am sorry to inform you that the patch is not making the testsets behave better. In fact, the test stops much... Ovidiu Maxiniuc

05:10 PM Bug #5056: Temp-tables and unique indexes

Ovidiu, please test whether the attached patch resolves your original issue(s). It gets both of the test cases you pr... Eric Faulhaber

05:00 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Please don't. If we were starting from scratch, we could consider it, but the changes you sh... Igor Skornyakov

04:44 PM Feature #1587: implement full support for word indexes

Please don't. If we were starting from scratch, we could consider it, but the changes you should be making to DDL gen... Eric Faulhaber

04:15 PM Feature #1587: implement full support for word indexes

As I can see at this moment FWD has a dependency on Apache Velocity. Can I use it for DDL generation? This will make ... Igor Skornyakov

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

I've resolved the issues described in #1587-349, implemented the generation of the word tables with indices/constrain... Igor Skornyakov

03:13 PM Feature #4022: upgrade to a newer PostgreSQL release

> * Did the package come out of the standard Ubuntu repos? Or did you have to add a PPA to the system?
Ubuntu.
... Stanislav Lomany

01:55 PM Feature #4022: upgrade to a newer PostgreSQL release

>> Were you able to leverage the pre-built PL/Java binaries?
>
> I installed PL/Java package using apt, along with ... Greg Shah

02/17/2021

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

Eric Faulhaber wrote:
> Igor Skornyakov wrote:
> > I've noticed two things regarding custom extends.
> > # If the ... Igor Skornyakov

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

Igor Skornyakov wrote:
> I've noticed two things regarding custom extends.
> # If the number of the @<extent-field@... Eric Faulhaber

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

I've noticed two things regarding custom extends.
# If the number of the @<extent-field@ subnodes on the .hints file... Igor Skornyakov

02/16/2021

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

Eric Faulhaber wrote:
> No problem. The annotation for the @wiext@ index looks correct to me as is.
Well, formally ... Igor Skornyakov

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

Igor Skornyakov wrote:
> I'm talking about @name = "fextFirst", legacy = "f-ext"@. The word table name was also ba... Eric Faulhaber

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

Eric Faulhaber wrote:
> I'm having trouble understanding the question. Please provide an example.
I mean the follow... Igor Skornyakov

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

Igor Skornyakov wrote:
> I've noticed that for word index with customized extent fields the value of the @name@ attr... Eric Faulhaber

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

I've noticed that for word index with customized extent fields the value of the @name@ attribute of the @IndexCompone... Igor Skornyakov

02/12/2021

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

Eric Faulhaber wrote:
> There are two aspects of performance we need to understand and measure from this testing:
>... Igor Skornyakov

12:44 PM Feature #1587: implement full support for word indexes

There are two aspects of performance we need to understand and measure from this testing:
* read (upon which the c... Eric Faulhaber

11:01 AM Feature #1587: implement full support for word indexes

Here is the suggested structure of the test table for performance testing of the new @CONTAINS@ support:
The test ta... Igor Skornyakov

02/10/2021

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

Eric Faulhaber wrote:
> I understand we need to correct the sort behavior for queries which use word indices, but I ... Igor Skornyakov

01:39 AM Feature #1587: implement full support for word indexes

Ovidiu Maxiniuc wrote:
> Igor Skornyakov wrote:
> > I have problems with removing @CONTAINS@ field from the @genera... Eric Faulhaber

02/09/2021

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

Suppressed using word index field for sorting.
Committed to 3821c revision 12004. Igor Skornyakov

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

Ovidiu Maxiniuc wrote:
> The @sort@ parameter is computed in @annotations/index_selection.rules@. Look for the @orde... Igor Skornyakov

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

Igor Skornyakov wrote:
> I have problems with removing @CONTAINS@ field from the @generated@ 'sort' parameter of the... Ovidiu Maxiniuc

02/08/2021

04:51 PM Feature #1587: implement full support for word indexes

Added runtime uppercasing of the CONTAINS UDF arguments (for temp-tables).
Committed to 3821c/11999. Igor Skornyakov

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

I have problems with removing @CONTAINS@ field from the @generated@ 'sort' parameter of the @AdaptiveQuery.initialize... Igor Skornyakov

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

Uppercasing the @CONTAINS@ arguments at conversion time removed in #3821/11998. Igor Skornyakov

09:26 AM Feature #1587: implement full support for word indexes

Added a subtask to #1587-327 which I've forgot to mention (Implement CONTAINS support for denormalized extent fields). Igor Skornyakov

04:28 PM Feature #5130: improve management of p2jpl.jar in deployment scripts

Eric Faulhaber wrote:
> Why do we use the most current @p2jpl.jar@ version from @${deploy.home.abs}/lib/@ only in th... Constantin Asofiei

03:49 PM Feature #5130: improve management of p2jpl.jar in deployment scripts

Does anyone know why we have this in the "template" @build_db.xml@ (not really a template, but it tends to get copied... Eric Faulhaber

02/05/2021

12:06 PM Feature #1587: implement full support for word indexes

This isn't about the word tables. I have to determine whether a word index comes into play with DMO validation and fl... Eric Faulhaber

12:00 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> One additional item, which I'll take as my responsibility, is to test how a word index plays... Igor Skornyakov

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

One additional item, which I'll take as my responsibility, is to test how a word index plays into validation/flushing... Eric Faulhaber

03:32 AM Feature #1587: implement full support for word indexes

Remaining work for the word indices support:
# Fix regressions introduced by word tables' support (if found).
# Rem... Igor Skornyakov

02/04/2021

04:09 PM Feature #1587: implement full support for word indexes

Word tables' scripts are idempotent now (can be run multiple times). This allows applying changes in constraints/indi... Igor Skornyakov

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

'Word indices are not supported' warning is suppressed in 3821c/11990 Igor Skornyakov

03:19 PM Feature #5130: improve management of p2jpl.jar in deployment scripts

Greg Shah wrote:
> Add a version UDF that is customized at build time similar to how we version FWD.
This alrea... Eric Faulhaber

01:09 PM Feature #5130: improve management of p2jpl.jar in deployment scripts

Clever! Greg Shah

01:05 PM Feature #5130: improve management of p2jpl.jar in deployment scripts

I use the following "quick and dirty" approach based on @direnv@ utility in the situations when additional steps are ... Igor Skornyakov

12:51 PM Feature #5130: improve management of p2jpl.jar in deployment scripts

Our current devops scripting is implemented outside of FWD. We use Apache @ant@ to script a range of conversion proj... Greg Shah

12:40 PM Feature #5130 (Rejected): improve management of p2jpl.jar in deployment scripts

Greg Shah

02/02/2021

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

Igor Skornyakov wrote:
> I've just realized that the trick with uppercasing at the database side required additional... Igor Skornyakov

02/01/2021

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

I've just realized that the trick with uppercasing at the database side required additional precautions. The PK/uniqu... Igor Skornyakov

09:22 AM Feature #4307 (Closed): DMO conversion changes

Branch 4011e was merged to trunk rev 11348. Eric Faulhaber

09:21 AM Feature #4020 (Rejected): reduce work Hibernate does flushing session

This task is moot with the removal of Hibernate in trunk rev 11348. Eric Faulhaber

09:18 AM Feature #4016 (Closed): replace portions of Hibernate which are non-performant

Hibernate was removed as of trunk rev 11348. Eric Faulhaber

01/29/2021

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

Eric Faulhaber wrote:
> You are referring to the "search-expression" portion of the CONTAINS operation, correct? Are... Igor Skornyakov

04:41 PM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> The only thing from the planned ones, for now, is removing the @CONTAINS@ operator expres... Eric Faulhaber

04:05 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > Can I continue using 1587b or should create a new branch fro... Igor Skornyakov

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

Igor Skornyakov wrote:
> Can I continue using 1587b or should create a new branch from 3821c?
You should not us... Eric Faulhaber

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

Branch 1587b was merged into 3821c revision 11969.
Can I continue using 1587b or should create a new branch from 3... Igor Skornyakov

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

Eric Faulhaber wrote:
> Have you tested the import with the customer application which previously was failing with t... Igor Skornyakov

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

Branch 1587b was rebased to 3821c rev. 11968
Pushed up to revision 11993.
The only thing from the planned ones... Igor Skornyakov

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

Igor Skornyakov wrote:
> 1. Removed warning 1688 at runtime
> 2. Added support for word index on extent field (Post... Eric Faulhaber

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

1. Removed warning 1688 at runtime
2. Added support for word index on extent field (PostgreSQL and H2, permanent tab... Igor Skornyakov

08:52 AM Bug #5121: Converted temp table should be using the legacy name instead of the converted name in ...

Saw this message logged: @Unable to locate shared temp-table or work-table definition for table <converted tablename>... Roger Borrello

08:51 AM Bug #5121 (New): Converted temp table should be using the legacy name instead of the converted na...

Roger Borrello

07:02 AM Feature #3958 (Review): BUFFER-COPY optimization

Added the @setActiveBuffer@ and @resetActiveBuffer@ with 3821c/rev. 11966. Beside those changes, I added @BaseRecord.... Adrian Lungu

07:41 PM Feature #4397: add database attrs, methods and options

Eric Faulhaber wrote:
> Code review 4397a/11958:
> @RecordBuffer.setCurrentRecord@ being non-private is still a pro... Ovidiu Maxiniuc

07:11 PM Feature #4397: add database attrs, methods and options

Code review 4397a/11991:
Continuing the discussion from #5056-14, I'm still convinced the @BufferImpl.validate()@ ... Eric Faulhaber

07:12 PM Feature #3574: finish implementation of temp-table XML support

Ovidiu Maxiniuc wrote:
> I re-did the rebase and re-commit earlier so you might want to review these changes too).
... Eric Faulhaber

01/28/2021

05:11 PM Feature #3574: finish implementation of temp-table XML support

That is exactly what I feel in regard to @TableMapper@, too. It only have the advantage of being decoupled, but acces... Ovidiu Maxiniuc

04:34 PM Feature #3574: finish implementation of temp-table XML support

I really don't like the @TableMapper@ construct at all. I tried to rationalize its internals at one point long ago, w... Eric Faulhaber

08:31 PM Feature #3574: finish implementation of temp-table XML support

I started implementing a solution for the issue in note-11. As noted there, the problem in the fact that @TableMapper... Ovidiu Maxiniuc

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

Eric Faulhaber wrote:
> Is the import change (to uppercase in the database) safe across all dialects we currently su... Igor Skornyakov

04:18 PM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> This will require a simple change in the import. But, to make the word table work correct... Eric Faulhaber

04:11 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > Well, if changes in the conversion are allowed I can impleme... Igor Skornyakov

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

Igor Skornyakov wrote:
> Well, if changes in the conversion are allowed I can implement a workaround for import by... Eric Faulhaber

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

Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > I understand your point. However, the initial idea was not t... Igor Skornyakov

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

Igor Skornyakov wrote:
> I understand your point. However, the initial idea was not to change the conversion at al... Eric Faulhaber

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

Eric Faulhaber wrote:
> We should not be adjusting for conversion errors at runtime. If something is incorrectly add... Igor Skornyakov

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

We should not be adjusting for conversion errors at runtime. If something is incorrectly added by conversion, we shou... Eric Faulhaber

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

I understand that the incorrect @ORDER BY@ component is added at the @PreselectQuery.assembleHQL()@ method. The @Sort... Igor Skornyakov

10:00 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> There are two things that can cause a problem:
> # temp-tables with word index for an exte... Igor Skornyakov

09:35 AM Feature #1587: implement full support for word indexes

Greg Shah wrote:
> > uppercasing with LATIN1 database (#5082). This is a real problem with at least one large custom... Igor Skornyakov

09:24 AM Feature #1587: implement full support for word indexes

> uppercasing with LATIN1 database (#5082). This is a real problem with at least one large customer app.
Does 1587... Greg Shah

09:10 AM Feature #1587: implement full support for word indexes

Greg Shah wrote:
> Is 1587b safe for merge into 3821c? Does it work properly for the large customer application whi... Igor Skornyakov

09:01 AM Feature #1587: implement full support for word indexes

Is 1587b safe for merge into 3821c? Does it work properly for the large customer application which you tested? We a... Greg Shah

01:39 PM Feature #4397: add database attrs, methods and options

Code review 4397a/11958:
@RecordBuffer.setCurrentRecord@ being non-private is still a problem. See comments in #43... Eric Faulhaber

01/27/2021

05:04 PM Bug #5056: Temp-tables and unique indexes

Actually my first idea for @validate()@ was as simple as:... Ovidiu Maxiniuc

04:42 PM Bug #5056: Temp-tables and unique indexes

Ovidiu Maxiniuc wrote:
> Yes, the method implementation does not make sense. The caller will get nothing in return. ... Eric Faulhaber

04:16 PM Bug #5056: Temp-tables and unique indexes

Yes, the method implementation does not make sense. The caller will get nothing in return. Nice catch! I think it sho... Ovidiu Maxiniuc

04:15 PM Bug #5056: Temp-tables and unique indexes

BTW, with my local changes, when I change the call from @BufferImpl.validate@ to pass @true@ to @RB.validate(boolean)... Eric Faulhaber

03:50 PM Bug #5056: Temp-tables and unique indexes

Ovidiu Maxiniuc wrote:
> Does it make sense to check whether the buffer is @Temporary@ ? Because the permanent table... Eric Faulhaber

03:37 PM Bug #5056: Temp-tables and unique indexes

Does it make sense to check whether the buffer is @Temporary@ ? Because the permanent tables have all indexes in plac... Ovidiu Maxiniuc

03:15 PM Bug #5056: Temp-tables and unique indexes

Ovidiu Maxiniuc wrote:
> Yes, please add the change to 3821c. I inspected the code (the four places where @validateM... Eric Faulhaber

02:48 PM Bug #5056: Temp-tables and unique indexes

Yes, please add the change to 3821c. I inspected the code (the four places where @validateMaybeFlush()@ is called) an... Ovidiu Maxiniuc

02:29 PM Bug #5056: Temp-tables and unique indexes

The patch was based on knowing that the @Validation@ instance was invoked for the purpose of flushing, but your point... Eric Faulhaber

01:53 PM Bug #5056: Temp-tables and unique indexes

Just inspecting the code it looked fine. I rebased and run the testcases to be sure. I got different behaviour, but n... Ovidiu Maxiniuc

11:30 AM Feature #3958: BUFFER-COPY optimization

Adrian Lungu wrote:
> I noticed something off in the current @BaseRecord.setAllDatum()@ implementation. This is used... Eric Faulhaber

01/26/2021

04:40 PM Bug #5056 (Review): Temp-tables and unique indexes

I have committed to 3821c/11953 a fix for the failing test case in #5056-3. Please review. I put it in 3821c because ... Eric Faulhaber

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

There is some strange thing I've noticed regarding the generated @sort@ parameter of the @AdaptiveQuery.initialize()@... Igor Skornyakov

11:54 AM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Please see if you can come up with any test case which breaks this rule or which further ref... Igor Skornyakov

11:38 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> Greg Shah wrote:
> > I guess the leftmost contains word match is the most significant orde... Eric Faulhaber

10:32 AM Feature #1587: implement full support for word indexes

Ovidiu Maxiniuc wrote:
> [...]? I.e., do the other words in the field matter?
As far as I can see, it doesn't matte... Igor Skornyakov

10:27 AM Feature #1587: implement full support for word indexes

Greg Shah wrote:
> I guess the leftmost contains word match is the most significant ordering constraint. Then the n... Ovidiu Maxiniuc

10:21 AM Feature #1587: implement full support for word indexes

Greg Shah wrote:
> I guess the leftmost contains word match is the most significant ordering constraint. Then the n... Igor Skornyakov

10:13 AM Feature #1587: implement full support for word indexes

I guess the leftmost contains word match is the most significant ordering constraint. Then the next word match and s... Greg Shah

10:00 AM Feature #1587: implement full support for word indexes

The order of the records in case of more complicated queries (see #1587-291) is less obvious. Consider the following ... Igor Skornyakov

09:22 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> As well known, SQL standard explicitly says that in the absence of the @ORDER BY@ clause th... Igor Skornyakov

10:20 AM Feature #3574: finish implementation of temp-table XML support

> shouldn't error flag be cleared at the start of the next NO-ERROR?
No. Although we initially thought this was t... Greg Shah

09:45 AM Feature #3574: finish implementation of temp-table XML support

Greg Shah wrote:
> 1. A @NO-ERROR@ statement has its errors collected into the @ErrorManager.WorkArea.pendingErrorSt... Ovidiu Maxiniuc

08:25 AM Feature #3574: finish implementation of temp-table XML support

> My question is: where/when should the error flag be reset?
1. A @NO-ERROR@ statement has its errors collected in... Greg Shah

01/25/2021

05:53 PM Feature #3574: finish implementation of temp-table XML support

While thinking of the above issue I encountered the next one. Consider the 4GL code (ignore missing declarations):
<... Ovidiu Maxiniuc

04:29 PM Feature #3574: finish implementation of temp-table XML support

I have encountered the following issue: the @serialize-hidden@ attribute steals the value from another temp-table fie... Ovidiu Maxiniuc

05:23 PM Feature #1587: implement full support for word indexes

As well known, SQL standard explicitly says that in the absence of the @ORDER BY@ clause the order of the @SELECT@ re... Igor Skornyakov

04:49 PM Feature #1587: implement full support for word indexes

Ovidiu Maxiniuc wrote:
> Igor Skornyakov wrote:
> > Should I use @__iifext@ in the @ORDER BY@ clause? Does it make... Igor Skornyakov

04:45 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Hm, I did not look carefully enough at the DDL. The presence of the @tt1__5@ table means tha... Igor Skornyakov

04:42 PM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> Should I use @__iifext@ in the @ORDER BY@ clause? Does it make sense?
Did you add @ifext@... Ovidiu Maxiniuc

04:33 PM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> It seems this is a problem with index selection. See https://proj.goldencode.com/artifacts/j... Igor Skornyakov

04:31 PM Feature #1587: implement full support for word indexes

To be more explicit regarding the test case requirement, please add a primary index to your test case temp-table, whi... Eric Faulhaber

04:28 PM Feature #1587: implement full support for word indexes

Hm, I did not look carefully enough at the DDL. The presence of the @tt1__5@ table means that temp-tables are not den... Eric Faulhaber

04:26 PM Feature #1587: implement full support for word indexes

Ovidiu Maxiniuc wrote:
> @ifext@ was added to @order by@ clause because @wiext@ index was selected to 'drive' the qu... Igor Skornyakov

04:22 PM Feature #1587: implement full support for word indexes

It seems this is a problem with index selection. See https://proj.goldencode.com/artifacts/javadoc/latest/api/com/gol... Eric Faulhaber

04:05 PM Feature #1587: implement full support for word indexes

@ifext@ was added to @order by@ clause because @wiext@ index was selected to 'drive' the query. Normally this should ... Ovidiu Maxiniuc

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

Ovidiu Maxiniuc wrote:
> Igor Skornyakov wrote:
> > Looking how to fix the @ORDER BY@ clause. In fact, I do not com... Igor Skornyakov

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

Igor Skornyakov wrote:
> Looking how to fix the @ORDER BY@ clause. In fact, I do not completely understand why @uppe... Ovidiu Maxiniuc

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

I've re-worked the SQL generations for @CONTAINS@ for temporary tables with an extent field (see #1587-271). However,... Igor Skornyakov

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

Igor Skornyakov wrote:
> I'm changing the code at this moment and cannot provide the exact error but it was about ... Eric Faulhaber

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

Eric Faulhaber wrote:
> What does the converted code look like for this test case?... Igor Skornyakov

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

Igor Skornyakov wrote:
> Eric Faulhaber wrote:
> > I was hoping to keep @FqlToSqlConverter@ clean w.r.t. denormaliz... Eric Faulhaber

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

Igor, sorry, I missed your intermediate post. Digesting it now... Eric Faulhaber

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

Although this is excellent information to document, I do want to reiterate that I want to avoid putting denormalizati... Eric Faulhaber

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

Ovidiu Maxiniuc wrote:
> > From Igor:
> > I need this in the @FqlToSqlConverter.toSQL()@. There is no information a... Igor Skornyakov

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

Eric Faulhaber wrote:
> I was hoping to keep @FqlToSqlConverter@ clean w.r.t. denormalization knowledge, and to avoi... Igor Skornyakov

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

> From Igor:
> I need this in the @FqlToSqlConverter.toSQL()@. There is no information about DMOs at this point (at ... Ovidiu Maxiniuc

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

I was hoping to keep @FqlToSqlConverter@ clean w.r.t. denormalization knowledge, and to avoid additional lookups at t... Eric Faulhaber

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

From email...
---
>> From Igor:
>>
>> Do we have any repository for the temporary tables' DMOs like @Metadat... Eric Faulhaber

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

Greg Shah wrote:
> > It was my suggestion to deal with warning 1688 at runtime and Grep agreed with this (see #1587-... Igor Skornyakov

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

> It was my suggestion to deal with warning 1688 at runtime and Grep agreed with this (see #1587-227, #1587-228).
... Greg Shah

03:40 AM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Igor Skornyakov wrote:
> > How can I run the conversion to use denormalized extent fields?
... Igor Skornyakov

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

Igor Skornyakov wrote:
> How can I run the conversion to use denormalized extent fields?
> Thank you.
I just rem... Eric Faulhaber

03:27 AM Feature #1587: implement full support for word indexes

How can I run the conversion to use denormalized extent fields?
Thank you. Igor Skornyakov

03:19 AM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Igor Skornyakov wrote:
>
> > I'm working now on the extent fields in the @_temp@ database... Igor Skornyakov

03:16 AM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Regarding the SQL rewriting, are you sure the FQL code coming from the @HQLPreprocessor@ (we... Igor Skornyakov

03:14 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> I'm working now on the extent fields in the @_temp@ database support. Without this, the c... Eric Faulhaber

03:11 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> There are three places affected by the word tables' support
> # DDL generation
> # Dat... Eric Faulhaber

03:09 AM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Code review 1587b/11924:
>
> I've made various, minor formatting and javadoc fixes and co... Igor Skornyakov

03:02 AM Feature #1587: implement full support for word indexes

Igor Skornyakov wrote:
> Eric Faulhaber wrote:
> > Thanks for the details.
> >
> > Is the case of the @f_ext@ fi... Igor Skornyakov

02:58 AM Feature #1587: implement full support for word indexes

Code review 1587b/11924:
I've made various, minor formatting and javadoc fixes and committed these as rev 11925. O... Eric Faulhaber

02:45 AM Feature #1587: implement full support for word indexes

Eric Faulhaber wrote:
> Thanks for the details.
>
> Is the case of the @f_ext@ field being denormalized handled? ... Igor Skornyakov

01:53 AM Feature #1587: implement full support for word indexes

Thanks for the details.
Is the case of the @f_ext@ field being denormalized handled? If so, is it handled above th... Eric Faulhaber