You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
-
# SODA 1.0.4
2
-
Simple Oracle Document Access (SODA) is an API from Oracle for working with JSON in the Oracle Database. Although SODA is particularly powerful when it comes to JSON data, data of any other type is supported as well.
1
+
# SODA 1.0.5
2
+
Simple Oracle Document Access (SODA) is an API which allows you to use the Oracle Database as a NoSQL JSON document store. Although SODA is particularly powerful when it comes to JSON data, data of any other type is supported as well.
3
3
4
4
With the SODA architecture, your data is stored as documents, and documents are organized into collections. Each document contains the actual data, as well as additional information automatically maintained by SODA, such as unique key, last-modified timestamp, version, type, etc. SODA lets you create and store such collections of documents in the Oracle Database, and perform create, retrive, update, and delete (CRUD) operations on these documents, without needing to know Structured Query Language (SQL), or JDBC, or how the data is stored in the database. Essentially SODA provides a virtual NoSQL document store on top of your Oracle Database. Under the covers, a collection is stored as a regular Oracle Database table, and each document is stored as a row in the table. SQL access to the table using standard tools is still allowed.
Copy file name to clipboardExpand all lines: doc/Building-and-running-tests.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ the patch, including the post-installation step.
10
10
The test framework is located in the /test directory under the root SODA directory (the root SODA directory is the one containing LICENSE.txt file). It's built with JUnit and driven by Ant. The actual Java test files are in /test/src/oracle/json/tests/soda. To configure the database instance and the test framework, follow these steps (note that some of them require sysdba access).
11
11
12
12
**(1)** Build the source code (which includes downloading SODA dependencies), as described
13
-
in [Building the source code](https://github.com/oracle/soda-for-java/blob/master/doc/Building-source-code.md). Make sure you perform all steps described in this link. Specifically, make sure that the JAVA6HOME environment variable is set, and that the following jars are located in the /lib directory under the top level SODA directory (the one that contains LICENSE.txt):
13
+
in [Building the source code](https://github.com/oracle/soda-for-java/blob/master/doc/Building-source-code.md). Make sure you perform all steps described in this link. Specifically, make sure that the JAVA_HOME environment variable is set, and that the following jars are located in the /lib directory under the top level SODA directory (the one that contains LICENSE.txt):
14
14
15
-
*ojdbc6.jar (the JDBC jar that ships with Oracle database version 12.1.0.2)
Copy the downloaded JDBC jar to the /lib directory under the root SODA directory (the root SODA directory is the one containing LICENSE.txt file).
17
22
18
23
Other dependencies will be automatically downloaded by Ivy. You also have the
19
24
option to not use Ivy, and to download the dependencies manually (see "Building without Ivy" below).
20
25
21
26
The following instructions require setting various environment variables. They assume you're on Linux, and using the C Shell (csh). On other OSes, you would set environment variables analogously, using a mechanism appropriate for your specific operating system.
22
27
23
-
SODA builds using Java 6. Set the JAVA6HOME environment
24
-
variable to the JDK install directory. For example, assuming JDK6 is installed
25
-
under /jdk6, and you're using the C Shell (csh) on Linux, do:
28
+
Set the JAVA_HOME environment variable to the JDK install directory. At a minimum, JDK 6 is required. For example, assuming you are using JDK 8 installed under /jdk8, and you're using the C Shell (csh) on Linux, do:
// Insert the documents into a collection, one-by-one.
90
90
// The result documents contain auto-generated
@@ -159,27 +159,27 @@ Copy and paste this code into a file called testSODA.java. Then modify the "url"
159
159
160
160
To compile and run SODA Java applications, you need the following jars:
161
161
162
-
* ojdbc6.jar that ships with Oracle Database 12.1.0.2. Download it from [this page](http://www.oracle.com/technetwork/database/features/jdbc/default-2280470.html).
162
+
* ojdbc6.jar (for use with JDK 6) or ojdbc7.jar (for use with JDK 7 or 8) that ship with Oracle Database 12.1.0.2. Download it from [this page](http://www.oracle.com/technetwork/database/features/jdbc/default-2280470.html). These jars will work with Oracle Database 12.1.0.2 and above. Alternatively, if you are using JDK 8 and Oracle Database 12.2.0.1 and above, you can use ojdbc8.jar from [this page](http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-3110062.html).
163
163
164
164
* javax.json-1.0.4.jar. This is the JSR353 implementation, download it from [here](http://search.maven.org/remotecontent?filepath=org/glassfish/javax.json/1.0.4/javax.json-1.0.4.jar).
165
165
166
166
* orajsoda-version.jar. The SODA jar. Download the latest version [here](https://github.com/oracle/soda-for-java/releases).
167
167
168
-
Compile and run testSODA.java, making sure the necessary jars are in the classpath. For example, assuming you're in the directory where the jars are located, do:
168
+
Compile and run testSODA.java, making sure the necessary jars are in the classpath. JDK 6 or above is required. For example, assuming you're in the directory where the jars are located, and you are using ojdbc7.jar, do:
* Retrieving documents representing users with at least 300 friends *
180
180
181
-
{ "name" : "Mia", "friends" : "300" }
182
-
{ "name" : "Gloria", "friends" : "399" }
181
+
{ "name" : "Mia", "friends" : 300 }
182
+
{ "name" : "Gloria", "friends" : 399 }
183
183
184
184
This example illustrates two ways of retrieving documents from the collection: by using unique document keys, or by using QBEs. To find all users with at least 300 friends, the following QBE was used in the code above:
0 commit comments