Discussions
Categories
- 385.5K All Categories
- 4.9K Data
- 2.5K Big Data Appliance
- 2.4K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Wrapping on the rows (adding three dots "..." after 10 letters)

Hi all,
I have a question about the rapping. I have data on the table. And some data are less than other and some are so long which creates so many free spaces for other cells of the same rows (Please, see the attached screenshot to understand clearly). I want to make the big sized data in the cells little by adding three dots (...) at the end of the 10^th letter (example: qwertyuiopasdfghjkl --> regular. I want it like this: qwertyuiop... When i'd click on the 3 dots, it would show the rest of the data) -IN ADDITION, ANY NEW IDEAS ABOUT HOW NOT TO WRAP MAY ACCEPTED AND APPRECIATED!
Thanks a lot for your help!
Answers
-
Thanks for any help.
-
helpme_helpyou wrote:I have a question about the rapping. I have data on the table. And some data are less than other and some are so long which creates so many free spaces for other cells of the same rows
That suggests that there is something wrong with the data model or report design (or both)...
(Please, see the attached screenshot to understand clearly).
While the screen shot succeeds in channelling Jackson Pollock, in the absence of any visible data it does nothing to clarify the problem. Rather than flooding the forum with pointless and eye-wateringly obfuscated screen shots, you'd get much more effective help by reproducing your problems in a workspace on apex.oracle.com using non-sensitive data.
I want to make the big sized data in the cells little by adding three dots (...) at the end of the 10^th letter (example: qwertyuiopasdfghjkl --> regular. I want it like this: qwertyuiop... When i'd click on the 3 dots, it would show the rest of the data) -IN ADDITION, ANY NEW IDEAS ABOUT HOW NOT TO WRAP MAY ACCEPTED AND APPRECIATED!
-
Thanks for your comment,
I believe that there is nothing wrong with the data (model or design). There are justs the information which needs to kept private that's why i color them. (sorry if it eye-wateringly and seems pointless). I can't share the data but the problem.
I have data which has different sized information for each row. As i described in this questoin, some rows have multiple lines for one cell which makes that row to extend and that's why i want to add three dots at the end of the long row's cell's information.
Sorry again about the eye-wateringly screenshots
-
helpme_helpyou wrote:I believe that there is nothing wrong with the data (model or design). There are justs the information which needs to kept private that's why i color them.
Illustrate the problems with examples that use realistic but non-sensitive values. It is standard practice (and in many jurisdictions a legal requirement) to do this in development and test environments.
-
Thank you for your suggestions and tips. I'll follow them in the future. Please, see the following screenshot for more information about the question.
-
I do not have the answer to this problem but as I have shown you before making an example on the website is very beneficial in getting valid responses and help. I would highly suggest you listen to @fac586 Your example does not need to have the exact data or even totally relevant data. Just something to work with together to gain the understanding. Also, keep in mind the minor differences between 5.0.4 and 5.1.2.
My idea would be creating a tooltip based off the column but this would only be feasible for 1 column.
-
Thanks and i will try to make an example. Thank you @fac586 as well!
-
Hi @fac586 ,
I am sorry being late. @AdamJaws helped to create an example (thanks Adam). Can you please login and see the example table?
Samplelink
USR: FAC586
PASS: abc123
As an example, in the current one, MI VERSION is longer than others (In my case, PT PUPPETVARIABLEs is longest and ven has upto 40 new lines). Can You please help me with the solution?
I would really appreciate it!
Thank You!
-
helpme_helpyou wrote:As an example, in the current one, MI VERSION is longer than others (In my case, PT PUPPETVARIABLEs is longest and ven has upto 40 new lines).
This screams "denormalized data". It's already been established that LOCATION should be a treated as a separate entity, and that referential integrity is non-existent: Select List (two empty selection) on Apex 5.04
It's clear from the above that the same goes for PT_PUPPETVARIABLES. Also PT_PUPPETCLASSES and probably other attributes of this table. The only "solution" I'm therefore going to suggest at this stage is the creation of a third normal form data model before making any attempt to design user interfaces and create applications. Failure to do so will result in the data becoming harder and harder to maintain and analyse at every step.
-
Unfortunately, the answer to your question is to take a step back and reformulate the tables. Follow the links FAC586 provided above otherwise you will continue to have "simple" problems that will combine into bigger.