![]() | |
![]() |
| | Thread Tools | Display Modes |
#51
| |||
| |||
|
|
I don't see any trace of this report as an open action item but if this is a production affecting issue for you the most affective approach is to work directly with the support organization to assign priorities to engineering resources to address any bugs here. "GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com... Hi, Nick I read the document many time. In fact, I found and reported the bug to Tom slee that ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the base in last release. And I thought that you would fix the bug about ColumnSchema ( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ). Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC. I tested it in the forth EBF release. It does not work. You can see the trace in the first article. So I pose this problem here. Lin r |
#52
| |||
| |||
|
|
I don't see any trace of this report as an open action item but if this is a production affecting issue for you the most affective approach is to work directly with the support organization to assign priorities to engineering resources to address any bugs here. "GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com... Hi, Nick I read the document many time. In fact, I found and reported the bug to Tom slee that ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the base in last release. And I thought that you would fix the bug about ColumnSchema ( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ). Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC. I tested it in the forth EBF release. It does not work. You can see the trace in the first article. So I pose this problem here. Lin r |
#53
| |||
| |||
|
|
I don't see any trace of this report as an open action item but if this is a production affecting issue for you the most affective approach is to work directly with the support organization to assign priorities to engineering resources to address any bugs here. "GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com... Hi, Nick I read the document many time. In fact, I found and reported the bug to Tom slee that ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the base in last release. And I thought that you would fix the bug about ColumnSchema ( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ). Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC. I tested it in the forth EBF release. It does not work. You can see the trace in the first article. So I pose this problem here. Lin r |
#54
| |||
| |||
|
|
I don't see any trace of this report as an open action item but if this is a production affecting issue for you the most affective approach is to work directly with the support organization to assign priorities to engineering resources to address any bugs here. "GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com... Hi, Nick I read the document many time. In fact, I found and reported the bug to Tom slee that ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the base in last release. And I thought that you would fix the bug about ColumnSchema ( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ). Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC. I tested it in the forth EBF release. It does not work. You can see the trace in the first article. So I pose this problem here. Lin r |
#55
| |||
| |||
|
|
I don't see any trace of this report as an open action item but if this is a production affecting issue for you the most affective approach is to work directly with the support organization to assign priorities to engineering resources to address any bugs here. "GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com... Hi, Nick I read the document many time. In fact, I found and reported the bug to Tom slee that ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the base in last release. And I thought that you would fix the bug about ColumnSchema ( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ). Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC. I tested it in the forth EBF release. It does not work. You can see the trace in the first article. So I pose this problem here. Lin r |
#56
| |||
| |||
|
|
I don't see any trace of this report as an open action item but if this is a production affecting issue for you the most affective approach is to work directly with the support organization to assign priorities to engineering resources to address any bugs here. "GUO Lin" <guolin.mobi (AT) gmail (DOT) com> wrote in message news:ea20905d-2185-4bc3-b32c-bb55a2f10f17 (AT) f63g2000hsf (DOT) googlegroups.com... Hi, Nick I read the document many time. In fact, I found and reported the bug to Tom slee that ColumnSchema.COLUMN_DEFAULT_AUTOINC can not work when we reconnect the base in last release. And I thought that you would fix the bug about ColumnSchema ( COLUMN_DEFAULT_AUTOINC and COLUMN_DEFAULT_GLOBAL_AUTOINC ). Now the problem is about COLUMN_DEFAULT_GLOBAL_AUTOINC. I tested it in the forth EBF release. It does not work. You can see the trace in the first article. So I pose this problem here. Lin r |
![]() |
| Thread Tools | |
| Display Modes | |
| |