Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 234 Big Data Appliance
- 1.9K Data Science
- 449.7K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 157 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 387 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1K Español
- 1.9K Japanese
- 230 Portuguese
Default table filter for number view attribute doesn't validate if value is a number

Hi,
i have just noticed that for View object attributes (or Entities attributes) that are numbers(Integer,BigInteger,BigDecimal) a default table filter doesn't checks if the entered value is a number.
After entering a string of letters in a filter and hitting enter application stops and a "Invalid number" shows in a popup.
I know that this issue could be easily solved by adding a new InputText into Column filter facet and adding a converter for that InputText but in a big application like ours we would try to avoid this.
I am surprised that this even happens, i mean if a attribute is a Number that means no letters should be entered.
Also, if we supply a converter (On entity attribute or ViewObject attribute) why isn't it automatically added to filter component?
Is there a easy solution to this?
Anodyne also noticed this bug?
Thanks,
JDev: 12.2.1.2.0
Robert
Best Answer
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,234 Red Diamond
Robert, this is not a bug at all. The filter isn't just a filter but a 'Query by Example' or QBE in short.
You can ann something like '100 or 114' into the filter field and get all rows having 100 or 114 in the field. Here is a sample of this for the employee table
If there would be a restriction to numbers this would not be possible.
Timo
Answers
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,234 Red Diamond
Robert, this is not a bug at all. The filter isn't just a filter but a 'Query by Example' or QBE in short.
You can ann something like '100 or 114' into the filter field and get all rows having 100 or 114 in the field. Here is a sample of this for the employee table
If there would be a restriction to numbers this would not be possible.
Timo
-
Hi TImo,
i didn't know you can do that.
Still it should check if this can even go in the query cause if you write for example 'deqewq' you get an exception when processing sql select.
Than anything you do on the page throws this exception. It is really annoying.
Robert