Discussions
Categories
- 384.5K All Categories
- 2.5K Data
- 551 Big Data Appliance
- 1.9K Data Science
- 451.3K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 561 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.4K SQL & PL/SQL
- 21.4K SQL Developer
- 296.8K Development
- Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.5K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 186 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 164 Java 8 Questions
- 86K Java Programming
- 81 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
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 525 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
Import from CSV date masks
I'm importing date+time data from CSV files, and the import wizard doesn't warn about the data while proposing this format: "YYYY-MM-DD:HH24:MI:SS", when the proper format should be: "DD/MM/RRRR HH24:MI".
Why does the wizard not warn about the data with the proposed "YYYY-MM-DD:HH24:MI:SS" format?
Answers
-
I dunno, it sounds like a bug to me.
Can you share two lines of your CSV data that demonstrates the issue and I can take a look, assuming you're on latest of SQLDev (21.4.3)
-
I'm on version 21.4.2.
medidor,CicloDesc,FechaHora,KWH,KW,KVA,KVAR
5284288,202203,24/02/2022 23:15,73.656,294.624,318.6706371,121.44
5284288,202203,24/02/2022 23:30,77.902,311.608,338.1392986,131.296
-
We do our best to detect...
you can override our advice with the proper date function call format, which in this case would be
'DD/MM/YYYY HH24:MI'
-
Gracias!
