table data tab
click on field --> set focus
paste data like this:
'xxxxxxxxxxxxxxxxxxxxxxxxxxxx
yyyyyyyyyyyyyyyyyy'
linefeed inside !
save, i.e, set focus somewhere else.
See what is in that field, only 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx'
part !
bug ?
That's no bug: table data is not supposed to be in multiple lines.
If you need a linefeed in your data (offending various database rules, btw), you can add an encased linefeed code in the single line of data. Examples (depending on the language which later parses the data) could be
If you need a linefeed in your data (offending various database rules, btw), you can add an encased linefeed code in the single line of data. Examples (depending on the language which later parses the data) could be
,
or (for HTML) <br />
.
Nope.
table data tab
click on field --> set focus
paste data like this:
'xxxxxxxxxxxxxxxxxxxxxxxxxxxx
yyyyyyyyyyyyyyyyyy'
linefeed inside !
save, i.e, set focus somewhere else.
See what is in that field (PRES F2), only 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx'
part !
If you paste text with line feed into F2 window then it is OK.
table data tab
click on field --> set focus
paste data like this:
'xxxxxxxxxxxxxxxxxxxxxxxxxxxx
yyyyyyyyyyyyyyyyyy'
linefeed inside !
save, i.e, set focus somewhere else.
See what is in that field (PRES F2), only 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx'
part !
If you paste text with line feed into F2 window then it is OK.
jfalch,
we may venture into philosophic waters here ...
it has nothing to do with 'characters', but meaningful 'data':
a data field content which requires a linefeed represents two (or more) singular entities. As such, that offends the First Normal Form (and as result may also offend the Second Nominal Form, depending on data used).
Just because one can actually include line feeds (or an appropriate encased character) does not mean that it is valid per definition, especially when holding up- or downgrade-ability in mind. A stricter future version of MySQL could render totally chaotic results; even if the user switches to a different OS now *could* result in loss of data integrity as various OS use different LF entities). Encased LF chars also hold a secondary danger: dumping data to a CSV will likely end up in disaster as for example the semicolon mostly used with an encasement may be interpreted as field end designator ...
Using data fields in an inappropriate way in the end leads to failure or loss, or at least results in a massive increase in service time and bug tracking. Example: every website owner that is 'forced' to support the Microsoft IE browsers encounters such a problem nearly every day. IE breaks everything because MS coders believe that they do not have to fully stick to W3C guidelines. Result: umpteen 'dirty' browser fixes and numerous browser hacks to merely achieve what all other browsers render (more or less, sic!) correctly.
Don't get me wrong, I am *not* saying that BubikolRamios is committing a crime or is a total nutface, I am only pointing out that utilizing certain 'undocumented features' will most probably backfire sooner or later.
we may venture into philosophic waters here ...
it has nothing to do with 'characters', but meaningful 'data':
a data field content which requires a linefeed represents two (or more) singular entities. As such, that offends the First Normal Form (and as result may also offend the Second Nominal Form, depending on data used).
Just because one can actually include line feeds (or an appropriate encased character) does not mean that it is valid per definition, especially when holding up- or downgrade-ability in mind. A stricter future version of MySQL could render totally chaotic results; even if the user switches to a different OS now *could* result in loss of data integrity as various OS use different LF entities). Encased LF chars also hold a secondary danger: dumping data to a CSV will likely end up in disaster as for example the semicolon mostly used with an encasement may be interpreted as field end designator ...
Using data fields in an inappropriate way in the end leads to failure or loss, or at least results in a massive increase in service time and bug tracking. Example: every website owner that is 'forced' to support the Microsoft IE browsers encounters such a problem nearly every day. IE breaks everything because MS coders believe that they do not have to fully stick to W3C guidelines. Result: umpteen 'dirty' browser fixes and numerous browser hacks to merely achieve what all other browsers render (more or less, sic!) correctly.
Don't get me wrong, I am *not* saying that BubikolRamios is committing a crime or is a total nutface, I am only pointing out that utilizing certain 'undocumented features' will most probably backfire sooner or later.
Your video per mail reveals you have not just focused the cell, it is indeed in editing mode, with the one-line edit box. This Windows control is not able to get line feeds. You need to press F2 again, or the right "..." button in order to start the multi-line editor. Or, just focus the cell without editing it, press paste and you're done.
I can sympathise with Bubikol.
I had copied a multiline value from one cell to another, and had click the destination cell twice so I had a cursor to paste to. I didn't suspect that only the first line had copied across until my application started throwing errors :)
It's definitely something users need to look out for.
I had copied a multiline value from one cell to another, and had click the destination cell twice so I had a cursor to paste to. I didn't suspect that only the first line had copied across until my application started throwing errors :)
It's definitely something users need to look out for.
Please login to leave a reply, or register at first.