Issue 104346 - Pattern field must remove ending spaces and not fills up with blanks
Summary: Pattern field must remove ending spaces and not fills up with blanks
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 3.1
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-08-20 00:28 UTC by mhatheoo
Modified: 2020-03-06 16:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description mhatheoo 2009-08-20 00:28:48 UTC
the summary says it:

It is annoying that one needs to define the mask for the character-entry for the
whole expected length, but places that need no entry on actual data-entry will
be filled up with blanks.
(Like: MASK CCCCCCCCCC - entry ABC123 - should not ad four blanks/spaces)
Just leave it as entered - with 6 characters as in the example

Comment 1 Frank Schönheit 2009-08-20 07:12:50 UTC
are we talking 'bout pattern fields here?
Comment 2 mhatheoo 2009-08-20 18:14:03 UTC

no, not about patterns (like the examples __.__.2009 etc) but exclusively the
mask  to destinguish the allowed character-input (the first of the property-fields)
give it a try, and you will see what I mean: The cursor is behind the spaces
inserted by the system - that looks strange and and is not functional for editing .

Comment 3 Frank Schönheit 2009-09-02 12:25:14 UTC
So we *do* talk about pattern fields here :)

I still do not completely get you. What do you mean with "The cursor is behind
the spaces inserted by the system"? (You might want to take item 3 and 4 on more serious :) )

So, you enter an "Edit mask" of, say, "CCCCCCCC", leave the Literal masks empty,
enter a text like "abc", and the problem is that this is expanded to "abc     "
- yes?
Comment 4 mhatheoo 2009-09-04 00:33:09 UTC
yes - exactly like that

Comment 5 oooforum (fr) 2020-03-06 16:11:03 UTC
I confirm that pattern is recorded as is.

A string completed with ending spaces is not a problem.
You can use RTRIM in SQL to remove it.