Modying Data Via The Result Pane & F8 (Change In Behaviour?)

[Aidan Whitehall]

I noticed maybe one or two versions ago that there seems to be change in behaviour when you paste values into a cell in the Result pane.

Previously, you could run a query by pressing F8, left-click a cell in the Results pane, press Ctrl+V to update a cell's value and you'd see the “Data modified but not saved” warning. If you then clicked the Up or Down arrow, the data would be saved.

Now it appears that if you left-click once in a cell and paste a value, the new value is displayed in the cell but the “Data modified but not saved” warning does not appear. If you then click Up or Down and re-run the query, the value in the cell reverts to its original state.

To modify the data, you now have to click twice in a cell, selecting its contents. If you now press Ctrl+V & then Enter, the contents are altered and the “Data modified but not saved” message appears. Pressing the Up or Down arrow now saves the data.

Can this be confirmed by anyone else?

If so, can this either (1) be changed to the previous behaviour (my preference) or (2) can the new behaviour be changed so that the cell will not accept the pasting of the new value unless the user has clicked the cell twice?

Thanks!

[peterlaursen]

We will check this but please tell what the old and new versions you are referring to are exactly. In particular the new one.

[Aidan Whitehall]

'peterlaursen' wrote on '29:

We will check this but please tell what the old and new versions you are referring to are exactly. In particular the new one.

Sorry Peter, am using 8.4 Community. Am not sure if the previous version (which was the first one in which I noticed this) was 8.2 or 8.3 Community.

[peterlaursen]

We cannot reproduce this.

1) first execute SELECT * FROM a_table

2) now select the table in the RESULT TAB dropdown to make result set editable

3) click in a cell once and we can paste (but note that in ENUM/SET columns you cannot) and the (red) alerting works exactly like if data are inserted from keyboard.

Are we missing something here?  Or maybe you are trying with an ENUM column?

[Aidan Whitehall]

'peterlaursen' wrote on '31:

We cannot reproduce this.

[snip]

Are we missing something here?  Or maybe you are trying with an ENUM column?

I didn't realise I'd hit upon a particular set of circumstances where this seems to manifest itself.

Have just gone through the steps again and found that it happens when you:

• execute the SQL statement by pressing F8, or press F9 and select the table name in the drop-down, and then
• paste a value into a date field where the retreived value is NULL (this appears to be the important factor)

The format of the value I was pasting is 2010-01-01 00:00:00

Hope this helps.

[Khushboo]

Issue confirmed as described. This is a known issue if the cell value is (NULL). It has been fixed in 8.5Beta3 we released last week. Can you please verify the fix in your environment?

Thank you for reporting.

Regards,

Khushboo

[Aidan Whitehall]

'Khushboo' wrote on '31:

Issue confirmed as described. This is a known issue if the cell value is (NULL). It has been fixed in 8.5Beta3 we released last week. Can you please verify the fix in your environment?

Yes, 8.5 beta 3 does fix this.

Thanks for your help!

[Author]

Posts