FWD » Core Development » Database

09/23/2019

04:22 PM Support #3871: determine how to change codepages/locales during import

It seems that H2 or PostgreSQL should have the same issue when importing UTF-8 dumps. OK. I will test PostgreSQL. It ... Sergey Ivanovskiy

03:29 PM Support #3871: determine how to change codepages/locales during import

Sergey Ivanovskiy wrote:
> This configuration
> [...]
> doesn't work too.
What exactly is not working? If ther... Eric Faulhaber

03:27 PM Support #3871: determine how to change codepages/locales during import

Debug into the @PatternEngine@ to see why it is failing. Greg Shah

03:16 PM Support #3871: determine how to change codepages/locales during import

This configuration ... Sergey Ivanovskiy

02:48 PM Support #3871: determine how to change codepages/locales during import

This ant task works properly for this project:... Sergey Ivanovskiy

02:39 PM Support #3871: determine how to change codepages/locales during import

Yes, command line is wrong. It seems like @data/namespace encode2.p2o@ should not have a space in it. Greg Shah

02:11 PM Support #3871: determine how to change codepages/locales during import

Greg Shah wrote:
> Please see #4279-91 for how to fix the unicode character escape sequence. I don't know what is w... Sergey Ivanovskiy

09/22/2019

04:30 PM Support #3871: determine how to change codepages/locales during import

Please see #4279-91 for how to fix the unicode character escape sequence. I don't know what is wrong with the other ... Greg Shah

03:03 AM Support #3871: determine how to change codepages/locales during import

The fragment of the converted program looks incorrect too... Sergey Ivanovskiy

02:20 AM Support #3871: determine how to change codepages/locales during import

I created a 4GL databases @encode2.db@ using @UTF-8@ encoding based on @C:\Progress\OE116_64\prolang\utf\ICU-ru.df@. ... Sergey Ivanovskiy

09/20/2019

02:48 PM Support #3871: determine how to change codepages/locales during import

Sergey Ivanovskiy wrote:
> Are these statements correct that @-cpinternal@ code page is used for character variables... Greg Shah

02:00 PM Support #3871: determine how to change codepages/locales during import

and @proutil encode1.db -C idxbuild all -cpinternal UTF-8@ was successful. It seems that for UTF-8 database encoding ... Sergey Ivanovskiy

01:50 PM Support #3871: determine how to change codepages/locales during import

I used this command to rebuild indices for UTF-8 database and please look what was the output
@proutil encode1.db -C... Sergey Ivanovskiy

01:45 PM Support #3871: determine how to change codepages/locales during import

Are these statements correct that @-cpinternal@ code page is used for character variables and fields and @-cpstream@ ... Sergey Ivanovskiy

07:05 AM Support #3871: determine how to change codepages/locales during import

Some other things to check:
* to access the data dump, you need to start the procedure editor; what happens if you ... Constantin Asofiei

06:18 AM Support #3871: determine how to change codepages/locales during import

First step I think is to create a database in 4GL with non-default codepage/locale, add some records with non-ASCII c... Constantin Asofiei

06:09 AM Support #3871: determine how to change codepages/locales during import

What should be done in order to test solutions for this task? Sergey Ivanovskiy

06:07 AM Support #3871 (WIP): determine how to change codepages/locales during import

Sergey Ivanovskiy

05:54 AM Support #3871: determine how to change codepages/locales during import

It follows that within @ImportWorker@ namespace @DataFileReader.processPscHeader()@ fills @encoding@ field and this f... Sergey Ivanovskiy

09/19/2019

06:26 PM Feature #4323: parse full FQL statements and convert them to SQL

In a recent email, you noted you had added support for field/column aliases. I'm not sure whether you were referring ... Eric Faulhaber

06:13 PM Feature #4323: parse full FQL statements and convert them to SQL

Ovidiu Maxiniuc wrote:
> Two questions I thought about but I do not have the answer yet:
> * how to handle EXTENTS ... Eric Faulhaber

10:44 AM Feature #4307: DMO conversion changes

The @TempTableRecord@ methods are not directly accessed by the business logic. Instead they are accessed only interna... Ovidiu Maxiniuc

09/18/2019

04:33 PM Feature #4307: DMO conversion changes

Let me ask what I'm really trying to understand... Do the temp-table DMO proxies used by business logic ever need to ... Eric Faulhaber

04:15 PM Feature #4307: DMO conversion changes

Yes, you deduce correctly. @TempTableRecord@ adds 5 new fields to standard record. You need to look at 4124a to see a... Ovidiu Maxiniuc

03:31 PM Feature #4307: DMO conversion changes

Ovidiu, I am trying to rationalize the DMO class/interface hierarchy to eliminate casting and differential logic to h... Eric Faulhaber

09/17/2019

05:18 PM Feature #4323: parse full FQL statements and convert them to SQL

Two questions I thought about but I do not have the answer yet:
* how to handle EXTENTS (in denormalized case things... Ovidiu Maxiniuc

12:24 AM Feature #4015 (Rejected): upgrade to a newer Hibernate release

We have decided to replace Hibernate with a bespoke ORM implementation instead. Eric Faulhaber

09/16/2019

05:54 PM Feature #2156: datetime-tz and hibernate

Greg Shah wrote:
> Ovidiu Maxiniuc wrote:
> > I would go for an unified solution for all dialects, even this duplic... Eric Faulhaber

05:31 PM Feature #2156: datetime-tz and hibernate

Stanislav, please create a branch from 4124a and work on that. Don't commit to 4124a (this is expected to be in trun... Constantin Asofiei

05:30 PM Feature #2156 (WIP): datetime-tz and hibernate

Ovidiu Maxiniuc wrote:
> I would go for an unified solution for all dialects, even this duplicating the offset infor... Greg Shah

03:12 PM Feature #4323: parse full FQL statements and convert them to SQL

Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > No, I'm talking about true [OUTER] JOIN ... ON ... syntax. This ... Eric Faulhaber

02:44 PM Feature #4323 (WIP): parse full FQL statements and convert them to SQL

Eric Faulhaber wrote:
> No, I'm talking about true [OUTER] JOIN ... ON ... syntax. This is a hole we have today, in ... Ovidiu Maxiniuc

02:01 PM Feature #4323: parse full FQL statements and convert them to SQL

Ovidiu Maxiniuc wrote:
> I was working with @join@ ing tables. I have the following issue: there is no @on@ keyword ... Eric Faulhaber

01:10 PM Feature #4323: parse full FQL statements and convert them to SQL

I was working with @join@ ing tables. I have the following issue: there is no @on@ keyword in HQL. In fact, it is not... Ovidiu Maxiniuc

09/14/2019

05:39 PM Bug #4325: Not flushing the newly created record to the database

In the following sequence ... Stanislav Lomany

04:59 PM Bug #4325 (New): Not flushing the newly created record to the database

Stanislav Lomany

11:59 PM Feature #4307: DMO conversion changes

Well done.
As noted originally, however, the DMO implementation classes should _not_ be emitted by default. The de... Eric Faulhaber

09/13/2019

07:35 PM Feature #4323: parse full FQL statements and convert them to SQL

An intermediary status. I added support for gathering data from tables/fields annotations in a cached data structure ... Ovidiu Maxiniuc

09/12/2019

04:26 PM Feature #4323: parse full FQL statements and convert them to SQL

I have investigated how much Hibernate is blended in FWD code: it's a lot: maybe 100 classes. Because of this, I thin... Ovidiu Maxiniuc

09/11/2019

06:44 PM Feature #4307: DMO conversion changes

Now the DMO Impl classes are not generated any more and DMO interfaces are constructed with DMO annotations.
To see ... Ovidiu Maxiniuc

03:08 PM Feature #4307: DMO conversion changes

Ovidiu Maxiniuc wrote:
> At a closer inspection, I see that the @extends DataModelObject@ is not present any more in... Eric Faulhaber

02:25 PM Feature #4307 (WIP): DMO conversion changes

At a closer inspection, I see that the @extends DataModelObject@ is not present any more in the new interface. Is thi... Ovidiu Maxiniuc

04:57 PM Feature #4323: parse full FQL statements and convert them to SQL

Ovidiu Maxiniuc wrote:
> A few questions before starting work:
> * we do not have a FWDQL generator. Should I use t... Eric Faulhaber

04:22 PM Feature #4323: parse full FQL statements and convert them to SQL

A few questions before starting work:
* we do not have a FWDQL generator. Should I use the current conversion (HQL) ... Ovidiu Maxiniuc

02:59 PM Feature #4323: parse full FQL statements and convert them to SQL

As part of the persistence performance overhaul, we are removing Hibernate from FWD. However, we still need an object... Eric Faulhaber

09/10/2019

03:39 PM Feature #4323 (WIP): parse full FQL statements and convert them to SQL

Eric Faulhaber

03:36 PM Feature #4012: replacing TCP/IP (AF_INET) sockets with Unix Domain Sockets (AF_UNIX) as PostgreSQ...

I think #4071 is caused by the use of AF_UNIX sockets, at least with the implementation noted above. This is a best g... Eric Faulhaber

09/09/2019

03:22 AM Feature #4307: DMO conversion changes

As part of our persistence performance overhaul, we are no longer going to emit source code for DMO implementation cl... Eric Faulhaber

03:10 AM Feature #4307 (Closed): DMO conversion changes

Eric Faulhaber

09/04/2019

05:54 PM Feature #3809: ProDataSet support

Ovidiu Maxiniuc wrote:
> You can drop it (all the lines). It was just for debug. I saw it, but you have already star... Constantin Asofiei

05:53 PM Feature #3809: ProDataSet support

Constantin Asofiei wrote:
> Ovidiu, you've added this to @dmo_common.rules@:
> [...]
> This produces lots of noise... Ovidiu Maxiniuc

05:51 PM Feature #3809: ProDataSet support

Ovidiu, you've added this to @dmo_common.rules@:... Constantin Asofiei

09/03/2019

03:42 PM Support #3871: determine how to change codepages/locales during import

>> 1. How do we control the encoding when we read the .d inputs? Do we have work here?
>
> Normally, one should not... Greg Shah

09/02/2019

06:15 PM Feature #3809: ProDataSet support

Constantin Asofiei wrote:
> Ovidiu, another question; for a data-source query like:
> [...]
>
> the 'next-rowid'... Ovidiu Maxiniuc

08/30/2019

11:11 AM Feature #2156: datetime-tz and hibernate

I would go for an unified solution for all dialects, even this duplicating the offset information for H2 and MSSQL: t... Ovidiu Maxiniuc

09:18 AM Feature #2156: datetime-tz and hibernate

It does look like PostgreSQL has a bad design for this use case (storing and honoring the offset):
https://dba.sta... Greg Shah

07:10 AM Feature #2156: datetime-tz and hibernate

I believe the big problem to implement single-column for DATETIME-TZ was the lack of support from H2.
Relative recen... Ovidiu Maxiniuc

08/29/2019

04:29 PM Bug #3379 (Review): do not copy index definitions when defining WORKFILE like TABLE

Vladimir Tsichevski

04:29 PM Bug #3379 (WIP): do not copy index definitions when defining WORKFILE like TABLE

The fix committed to the 4103a branch. The new revno is 11328. Vladimir Tsichevski

03:55 PM Feature #2156: datetime-tz and hibernate

All of our current databases support a single column that stores both the timestamp and offset:
* PostgreSQL has @... Greg Shah

02:20 PM Feature #2156: datetime-tz and hibernate

There's one other thing to add for @datetime-tz@ - its usage in indexes and sort clauses. Being a multi-column Hiber... Constantin Asofiei

08/28/2019

06:09 PM Feature #3809: ProDataSet support

As noted in a previous email, @__error-flag__@, @__origin-rowid__@, @__error-string__@, @__after-rowid__@ and @__row-... Ovidiu Maxiniuc

03:16 PM Bug #3379: do not copy index definitions when defining WORKFILE like TABLE

See the explanation and a proposed fix in #4103. Vladimir Tsichevski

01:53 AM Feature #3816: table and table handle parameter options

Constantin Asofiei wrote:
> An addition here: not only the default-buffer, any explicit buffer defined (non-dynamic)... Marian Edu

08/27/2019

09:17 AM Bug #3379: do not copy index definitions when defining WORKFILE like TABLE

Good, that makes it simpler. Please dig into @addEntries()@ to see how the indexes get copied. The @SchemaDictionar... Greg Shah

07:44 AM Bug #3379: do not copy index definitions when defining WORKFILE like TABLE

Greg Shah wrote:
> The 4GL docs don't show that the @USE-INDEX@ clause is allowed for @DEFINE WORK-TABLE@ but perh... Vladimir Tsichevski

07:29 AM Bug #3379: do not copy index definitions when defining WORKFILE like TABLE

@like_clause@ uses @SymbolResolver.addFieldsFrom()@ to search for the @LIKE table@ and load the fields using @SchemaD... Greg Shah

09:00 AM Feature #3816: table and table handle parameter options

@BIND@ can be used to bind a reference only table in the caller only if the called routine has an @OUTPUT@ parameter ... Marian Edu

08:26 AM Feature #3816: table and table handle parameter options

Marian Edu wrote:
> Constantin, the before-table as well as the default buffer handle (and the before-table's defaul... Constantin Asofiei

07:12 AM Feature #3816: table and table handle parameter options

Constantin, the before-table as well as the default buffer handle (and the before-table's default buffer handle) are ... Marian Edu

08/26/2019

07:22 PM Bug #3379: do not copy index definitions when defining WORKFILE like TABLE

Greg, what do you think? Assuming all indices are to be ignored in the copy as we were told, does the fix belong in t... Eric Faulhaber

01:30 PM Feature #3816: table and table handle parameter options

There's a new issue to consider; if the temp-table has a before-table, when passing this table (or its dataset) aroun... Constantin Asofiei

08/25/2019

05:09 PM Feature #3809: ProDataSet support

Ovidiu, another issue: DATASET:ACCEPT-CHANGES is not working for static datasets, as you are emulating this via the @... Constantin Asofiei