Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
You need to be logged in to view a user's profile.
View Replies (7)

Resolved PB2017 R2 Changing SQL in DataWindow changes GUI

  1. Issue
0
Votes
Undo
  1. Arthur Hefti
    Arthur Hefti
  2. PowerBuilder
  3. Thursday, 1 February 2018 10:15 AM UTC
When I change something in the SQL part of the DataWindow, e.g. add a new column the dbname property changes and returning the the design part places all these changed columns new. 
Any idea what the reason could be.
 
Regards
Arthur
 
SQL:
SELECT 
unfallkat = ' ',
 
PB 2017
 column=(type=char(1) updatewhereclause=yes name=unfallkat dbname="unfallkat" )
 
PB 2017 R2
 column=(type=char(1) updatewhereclause=yes name=unfallkat dbname="compute_0010" )
  1. Data
PB2017R2 & GIT
advguisample question
Responses (7)
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Monday, 12 February 2018 06:55 AM UTC
  2. PowerBuilder
  3. # 1

Hi,

We are very sorry for the issue you are experiencing and the inconvenience this has caused you. 

Now our team is preparing an emergency patch for this issue. The patch is under final validation.  We will make it available to all users  (tentatively on or before February 16, 2018) in our Download portal along with the download link of PowerBuilder 2017 R2.

Regards.. Ken

Comment
There are no comments made yet.
Arthur Hefti
Arthur Hefti Accepted Answer Pending Moderation
  1. Friday, 9 February 2018 04:52 AM UTC
  2. PowerBuilder
  3. # 2

As now after a week this is a confirmed but I would like to know when we could expect a fix. The workaround described is fine for occasionally changes in DataWindows but not for real live.

This serious bug prevents us from using R2 which has a big impact of a big project at a customer as they plan to move the whole repository (not PB only) from an internal SVN server to hosted GIT in February which would allow other developers work on the project without having access to the company network. We need to convince our customer to postpone this  move as otherwise the PB programmers end up working with notepad in the source.

We definitely need a release date for this fix. 

Comment
There are no comments made yet.
Frode Guldberg
Frode Guldberg Accepted Answer Pending Moderation
  1. Wednesday, 7 February 2018 15:33 PM UTC
  2. PowerBuilder
  3. # 3

This is a showstopper for us too, had to uninstall R2.

Why change this behavior in the first place?

 

Please fix this, and return to the old logic for dbname and name.

 

 

Frode Guldberg

Comment
There are no comments made yet.
Heiko Bergner
Heiko Bergner Accepted Answer Pending Moderation
  1. Monday, 5 February 2018 08:15 AM UTC
  2. PowerBuilder
  3. # 4

Hello,

as Arthur mentioned, this behavior makes the PB 2017 R2 absolutly useless for us too.

That the existing fields are inserted as new fields is only one problem.

Our program makes heavy use of the describe command dbname (e.g. dw_1.describe(ls_parm+".dbname")
and to access fields. So if one fieldname is not existing anymore, the whole program may not work anymore.

This new "feature" has to be fixed as soon as possible.

 

Best regards,

Heiko

 

Comment
There are no comments made yet.
Tobias Roth
Tobias Roth Accepted Answer Pending Moderation
  1. Friday, 2 February 2018 13:32 PM UTC
  2. PowerBuilder
  3. # 5

Just tried that testcase, i dont have the problem. 

I tried:
'' as column_name1
and
column_name1 = ' '

Comment
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 1 February 2018 15:27 PM UTC
  2. PowerBuilder
  3. # 6

Hi Arthur,

Release Bulletin for PB 2017 R2, section 2.3 describes this exact issue in DB-Name for computed fields.

/Michael

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 2 February 2018 05:05 AM UTC
Oh dear ...    Yes, that is really, really bad.   



If an SQL Clause uses an "AS MyName" then the DW should preserve the column as "MyName"!



 



 

  1. Helpful
Tobias Roth
  1. Tobias Roth
  2. Friday, 2 February 2018 10:11 AM UTC
Are there any plans for fixing that problem?

We can't upgrade to R2 as long as the problem exists 

  1. Helpful
Roy Bungert
  1. Roy Bungert
  2. Wednesday, 7 February 2018 09:42 AM UTC
Any news about this issue? This is a real showstopper for us for changing to R2.



 A lot of our dws are already destroyed because all computed fields of a DW-SQL are removed from the dw and added at a new position!



 

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 February 2018 15:14 PM UTC
  2. PowerBuilder
  3. # 7

Hi Arthur;

   To me technically, the R2 syntax looks proper as unfallkat  is an SQL computed column.

Does the DWO still run OK?

Regards ... Chris

Comment
Arthur Hefti
  1. Arthur Hefti
  2. Thursday, 1 February 2018 15:43 PM UTC
All the columns with the new DB name are deleted (if on the GUI) and placed again on the GUI like I when I create a new DataWindow. This means I can't edit any DataWindow with comuted columns.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.