FWD » Core Development » Database

07/26/2014

02:52 PM Bug #2344: invalid scoping for dynamic buffers

Stanislav Lomany wrote:
> @4) Department CREATE@ output:
>
> [...]
You have to run "1) Department Type CREATE.... Eric Faulhaber

02:43 PM Bug #2344: invalid scoping for dynamic buffers

Code review 0725a:
Looks good. Please note that Vadim has a change to @RecordBuffer@ for #2331 (@vmn_upd20140723a.... Eric Faulhaber

07/25/2014

06:09 PM Bug #2344: invalid scoping for dynamic buffers

@4) Department CREATE@ output:... Stanislav Lomany

05:57 PM Bug #2344: invalid scoping for dynamic buffers

Yes. I ignored it:... Stanislav Lomany

05:53 PM Bug #2344: invalid scoping for dynamic buffers

Are you getting this after running @dbuf-scope1.p@?... Eric Faulhaber

05:52 PM Bug #2344: invalid scoping for dynamic buffers

Stanislav Lomany wrote:
> > Make sure the department_code_create API is not regressed
>
> Am I missing some files... Eric Faulhaber

05:49 PM Bug #2344: invalid scoping for dynamic buffers

> Make sure the department_code_create API is not regressed
Am I missing some files or do you mean 4) Department C... Stanislav Lomany

04:53 PM Bug #2344: invalid scoping for dynamic buffers

Good. Greg Shah

04:47 PM Bug #2344: invalid scoping for dynamic buffers

I use... Stanislav Lomany

04:27 PM Bug #2344: invalid scoping for dynamic buffers

Please check your testcases into testcases/uast/dynamic_buffer/. Greg Shah

04:26 PM Bug #2344: invalid scoping for dynamic buffers

> > Dynamic buffers for permanent tables should have global scope.
>
> Are you sure about this? How did you confir... Stanislav Lomany

04:25 PM Bug #2344: invalid scoping for dynamic buffers

Pending a reply to my last question...
Stanislav Lomany wrote:
> Fixes my testcases, #2329 and parameter_code_sea... Eric Faulhaber

04:06 PM Bug #2344: invalid scoping for dynamic buffers

Stanislav Lomany wrote:
> Dynamic buffers for permanent tables should have global scope.
Are you sure about this?... Eric Faulhaber

06:20 AM Bug #2344: invalid scoping for dynamic buffers

Fixes my testcases, #2329 and parameter_code_search (I guess #2331 is about that?). Note that I've altered ... Stanislav Lomany

11:17 AM Bug #2295: In Progress output parameters ignore decimal precision

I don't think anything more is needed right now. Eric will make the call on this soon. We will probably have to fix... Greg Shah

11:08 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek Cihlar wrote:
> If other storage systems are planned to be supported I think these should be tested as well. I ... Hynek Cihlar

08:14 AM Bug #2337: trigger scanning defect

After lots of failing tests I asked for Constantin's opinion and he confirmed that the update is safe for commit.
Lu... Ovidiu Maxiniuc

07/24/2014

08:23 AM Bug #2344: invalid scoping for dynamic buffers

... Stanislav Lomany

08:14 AM Bug #2344: invalid scoping for dynamic buffers

Dynamic buffers for permanent tables should have global scope.... Stanislav Lomany

07:45 AM Bug #2344 (Closed): invalid scoping for dynamic buffers

Stanislav Lomany

07/23/2014

08:57 AM Bug #2295: In Progress output parameters ignore decimal precision

Constantin Asofiei wrote:
> Hynek Cihlar wrote:
> > Constantin Asofiei wrote:
> > * @display@ shows the decimal va... Hynek Cihlar

02:56 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek Cihlar wrote:
> Constantin Asofiei wrote:
> * @display@ shows the decimal value according to field's format d... Constantin Asofiei

07/22/2014

06:27 PM Bug #2295: In Progress output parameters ignore decimal precision

Constantin Asofiei wrote:
> Please try to find where the field's DECIMALS clause is forced: assign operator, buffer-... Hynek Cihlar

03:04 PM Bug #2295: In Progress output parameters ignore decimal precision

If other storage systems are planned to be supported I think these should be tested as well. I can imagine (and I act... Hynek Cihlar

07/21/2014

09:01 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek, please confirm that your test cases showing the unconstrained storage behavior work the same way on Progress 9... Eric Faulhaber

03:31 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek Cihlar wrote:
> What semantics @MAX-WIDTH@ holds anyway? I didn't find any useful documentation explaining the... Constantin Asofiei

07/20/2014

03:16 PM Bug #2295: In Progress output parameters ignore decimal precision

Constantin Asofiei wrote:
> OK, I think I understand what you mean now. What you need to test is this: change the ... Hynek Cihlar

08:02 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek Cihlar wrote:
> By @MAX-WIDTH@ did you mean the default number of decimal places, i.e. 10? The maximum number ... Constantin Asofiei

07/19/2014

07:49 PM Bug #2295: In Progress output parameters ignore decimal precision

Constantin Asofiei wrote:
> Please try to find where the field's DECIMALS clause is forced: assign operator, buffer-... Hynek Cihlar

05:03 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek Cihlar wrote:
> When the data is read into another buffer the buffer will still hold the unconstraint decimal ... Constantin Asofiei

07/18/2014

08:25 AM Bug #2295: In Progress output parameters ignore decimal precision

When the data is read into another buffer the buffer will still hold the unconstraint decimal value. I tried your sam... Hynek Cihlar

04:21 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek, please check the following too:
# what happens if the record (for which the field's decimals doesn't match th... Constantin Asofiei

07/17/2014

05:24 PM Bug #2295: In Progress output parameters ignore decimal precision

Greg Shah wrote:
> Please post the testcase(s) that you used to find this strange behavior. I'd like to see how appl... Hynek Cihlar

04:46 PM Bug #2295: In Progress output parameters ignore decimal precision

Please post the testcase(s) that you used to find this strange behavior. I'd like to see how applications might rely... Greg Shah

04:36 PM Bug #2295: In Progress output parameters ignore decimal precision

Constantin Asofiei wrote:
> Please double-check how this behaves with a physical table; use the p2j_test.df schema a... Hynek Cihlar

07/15/2014

02:24 PM Bug #2337: trigger scanning defect

There were no conversion differences (Except for the schema-triggers.xml file itself in src/aero/timco/majic/dmo).
T... Ovidiu Maxiniuc

10:32 PM Bug #2337: trigger scanning defect

Code review 0714a:
Looks good, please commit and distribute when this passes testing. Eric Faulhaber

07/14/2014

03:46 PM Bug #2337: trigger scanning defect

Attached the update that saves the @schema-trigger.xml@ to @src/{application path}/dmo@ directory to be further packa... Ovidiu Maxiniuc

02:16 PM Bug #2337: trigger scanning defect

Greg Shah wrote:
> ...we can always write a tool to generate the xml "cache" file from the annotations, such that it... Eric Faulhaber

10:56 AM Bug #2337: trigger scanning defect

In regard to the annotations vs xml file approach question, my preference is for the annotations approach. If the pe... Greg Shah

10:50 AM Bug #2337: trigger scanning defect

Code Review 0711a
I only reviewed the parser change. It looks good. Nice catch. Greg Shah

10:37 AM Bug #2337: trigger scanning defect

Greg: when Ovidiu posts the next update, would you please review the parser change? Eric Faulhaber

10:34 AM Bug #2337: trigger scanning defect

Let's keep all these alternatives in mind, but considering that it works well as is (I tested with the @schema-trigge... Eric Faulhaber

10:19 AM Bug #2337 (WIP): trigger scanning defect

I noticed that unintentionally I changed the status of this issue back to "Review". Reverted to WIP. Ovidiu Maxiniuc

07:15 AM Bug #2337 (Review): trigger scanning defect

I see tree solutions now, not sure which is the best:
1. the easiest would be to keep the current one, implemented i... Ovidiu Maxiniuc

03:22 PM Feature #2339: generate schema-triggers.xml from Java annotations at build time

Eric Faulhaber wrote:
> I understand @schema-triggers.xml@ is an artifact of conversion, and an intermediate form of... Ovidiu Maxiniuc

02:45 PM Feature #2339: generate schema-triggers.xml from Java annotations at build time

Eric Faulhaber wrote:
> ... and replacing the dots with slashes).
What I should have written was "... and replaci... Eric Faulhaber

02:42 PM Feature #2339: generate schema-triggers.xml from Java annotations at build time

Ovidiu Maxiniuc wrote:
> I was about to reply on 2337. I am not sure you understand the utility of @schema-triggers.... Eric Faulhaber

02:18 PM Feature #2339: generate schema-triggers.xml from Java annotations at build time

I was about to reply on 2337. I am not sure you understand the utility of @schema-triggers.xml@.
The xml file is c... Ovidiu Maxiniuc

02:10 PM Feature #2339: generate schema-triggers.xml from Java annotations at build time

See discussion in #2337, beginning at note 9, and particularly note 17.
The idea is to emit Java annotations relat... Eric Faulhaber

02:02 PM Feature #2339 (New): generate schema-triggers.xml from Java annotations at build time

Eric Faulhaber

07/13/2014

03:35 PM Bug #2295: In Progress output parameters ignore decimal precision

The case above from note 1 has been fixed by #2293. Hynek Cihlar

07/12/2014

06:27 PM Bug #2295 (WIP): In Progress output parameters ignore decimal precision

Hynek Cihlar

01:43 PM Bug #2337: trigger scanning defect

I converted the customer's server project. The @schema-triggers.xml@ file is left at the project root directory, but ... Eric Faulhaber

07/11/2014

03:35 PM Bug #2337 (WIP): trigger scanning defect

Code review 20140711a:
The only comment I have is about the change in approach when initializing the trigger manag... Eric Faulhaber

02:28 PM Bug #2337 (Review): trigger scanning defect

Uploaded fix for trigger issues:
- the @schema-trigger.xml@ improved in the second step
- @DatabaseTriggerManager@ ... Ovidiu Maxiniuc

11:32 AM Bug #2337: trigger scanning defect

Ah, OK. Sorry for the confusion I caused. Eric Faulhaber

11:30 AM Bug #2337: trigger scanning defect

I see, for the customer, @com/something/server/dmo@, it make more sense.
I was fooled by "directory's parent". I int... Ovidiu Maxiniuc

11:22 AM Bug #2337: trigger scanning defect

Ovidiu Maxiniuc wrote:
> I will add the rule for copying the file to @run/server@ and load it accordingly.
I foll... Eric Faulhaber

06:36 AM Bug #2337: trigger scanning defect

I found the cause why ASSIGNS are not converted correctly.
In the @progress.g@, in the @on_stmt@ function, the follo... Ovidiu Maxiniuc

05:00 AM Bug #2337: trigger scanning defect

Eric Faulhaber wrote:
> I would not add this to the root of the jar, if it is associated with a particular schema (@... Ovidiu Maxiniuc

07/10/2014

06:07 PM Bug #2337: trigger scanning defect

Ovidiu Maxiniuc wrote:
> Fixed the issue. It proved to be rather simple, just to add the class name (including packa... Eric Faulhaber

04:29 PM Bug #2337 (WIP): trigger scanning defect

Fixed the issue. It proved to be rather simple, just to add the class name (including package to current xml list of ... Ovidiu Maxiniuc

12:16 PM Bug #2337: trigger scanning defect

Because File.listFiles() does not work on jar locations, the initialization of the @DatabaseTriggerManager@ (gatherin... Ovidiu Maxiniuc

12:11 PM Bug #2337 (Closed): trigger scanning defect

Ovidiu Maxiniuc

07/09/2014

05:08 PM Bug #2336: TABLE-HANDLE FOR parameters for internal procedures

TABLE-HANDLE FOR parameters for internal procedures are not converted properly. @appserver-table-errors.p@ and @appse... Stanislav Lomany

05:04 PM Bug #2336 (New): TABLE-HANDLE FOR parameters for internal procedures

Stanislav Lomany

07/02/2014

06:27 AM Bug #2327: Wrong values initialized by field initializer

This is a database issue more than a base language issue.
Eric will determine if this needs to be worked now, or i... Greg Shah

06:20 AM Bug #2326: Reference to the extent value of a field is emitted as a constant

This task is related to database conversion more than base language.
It does not need to be worked on right now. Greg Shah

03:51 AM Bug #2295: In Progress output parameters ignore decimal precision

Hynek Cihlar wrote:
> The case above from note 1 has been fixed as part of the issue #2293, and about to be released... Constantin Asofiei

07/01/2014

05:15 PM Bug #2295: In Progress output parameters ignore decimal precision

The case above from note 1 has been fixed as part of the issue #2293, and about to be released.
A similar case exi... Hynek Cihlar

09:41 AM Feature #2312: match Progress collation in a SQL Server database

I have run some scans over the database dump from lincon01, indexing the occurrences for each character in strings. I... Ovidiu Maxiniuc

06/30/2014

05:39 AM Bug #2327: Wrong values initialized by field initializer

The following program... Hynek Cihlar

05:38 AM Bug #2327 (New): Wrong values initialized by field initializer

Hynek Cihlar

03:28 AM Bug #2326: Reference to the extent value of a field is emitted as a constant

Hynek Cihlar wrote:
> If I am correct, fields can be declared as determinate extents only (with a constant extent si... Constantin Asofiei

06/29/2014

05:09 PM Bug #2326: Reference to the extent value of a field is emitted as a constant

If I am correct, fields can be declared as determinate extents only (with a constant extent size) hence this issue ma... Hynek Cihlar

05:03 PM Bug #2326: Reference to the extent value of a field is emitted as a constant

The 4GL code... Hynek Cihlar

04:54 PM Bug #2326 (New): Reference to the extent value of a field is emitted as a constant

Hynek Cihlar

06/27/2014

06:29 PM Feature #2312: match Progress collation in a SQL Server database

Please choose from the available collations the ones you feel are the closest, practical matches for Progress' collat... Eric Faulhaber