![]() ![]() There are however, some reasons you might need to go ‘thick.’ You can read all about how this works here.īut now, I can have connections in a single instance of SQL Developer going with both THIN and THICK configurations. Nothing else needed to install or configure. ![]() thick = mix of Java and native compiled libraries via Oracle Client or Instant Client, required for some use cases like RADIUS authenticationĪnd it’s totally fine to usually just go with THIN.thin = PURE JAVA, what most people should be using.Just to back up a bit, your options for connecting to Oracle with our JDBC driver are: If I enable it here, it will mean EVERY Oracle connection going forward will be of type OCI. Previously, SQL Developer would be configured for THICK or THIN connections, application wide, via the ‘Use OCI’ preference on the Advanced page. Now about that Advanced page you still see there, I want to call out a new feature exposed there: You can now define connections as THICK or THIN. ![]() Proxy User info is moved up top next to the rest of the username stuff – it’s no longer on an advanced pop up dialog. The name and color of the connection is up top now, and it’s hopefully less likely you’ll type your password into the username input area by accident! One change you’ll see right away is a simpler connection dialog: This is how it looks in version 19.1 Today I want to highlight some changes we made to how you define your connections. Version 19.1 of SQL Developer, SQLcl, Data Modeler, and ORDS are now all available, and you can expect many posts over the next few weeks to cover all the new goodies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |