[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing (see comment 9)

2023-09-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 Buovjaga changed: What|Removed |Added Severity|normal |enhancement Ever confirmed|0

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #9 from Robert Großkopf --- (In reply to jcsanz from comment #8) > since it seems that the behavior is not incorrect, but different than > expected, should we classify the bug as NOTABUG? This would implement: Nothing should

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #8 from jcs...@libreoffice.org --- since it seems that the behavior is not incorrect, but different than expected, should we classify the bug as NOTABUG? -- You are receiving this mail because: You are the assignee for the

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #7 from Robert Großkopf --- (In reply to jcsanz from comment #6) > (In reply to Robert Großkopf from comment #5) > > > It is nice Firebird will save the view without changing the code to all > > existing field names as other

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #6 from jcs...@libreoffice.org --- (In reply to Robert Großkopf from comment #5) > It is nice Firebird will save the view without changing the code to all > existing field names as other databases would do (internal HSQLDB,

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #5 from Robert Großkopf --- (In reply to jcsanz from comment #4) > (In reply to Robert Großkopf from comment #3) > > > Don't know where to find the view definition in Firebird, but execute... > > The definitions and

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #4 from jcs...@libreoffice.org --- (In reply to Robert Großkopf from comment #3) > Don't know where to find the view definition in Firebird, but execute... The definitions and attributes of all tables and views are stored in

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #3 from Robert Großkopf --- (In reply to jcsanz from comment #1)> > 3. Edit in SQLview. In this case you are doing a *new definition* of the > view as the word *edit* suggest. No, I don't do anything *new*. I have opened

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #2 from jcs...@libreoffice.org --- (In reply to Robert Großkopf from comment #0) > Note: Views with internal HSQLDB will change the code while creating a view > from a query with > SELECT * FROM "tbl_person" > to > SELECT

[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing

2023-07-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #1 from jcs...@libreoffice.org --- I don't see any erroneous behavior. 1. Execute view viw_person --> Show 3 fields --> As you stated that is correct because the view was defined in that way (when the table had three fields).