Ruby Client for the Oracle Database@Google Cloud API
The Oracle Database@Google Cloud API provides a set of APIs to manage Oracle database services, such as Exadata and Autonomous Databases.
The Oracle Database@Google Cloud API provides a set of APIs to manage Oracle database services, such as Exadata and Autonomous Databases.
Actual client classes for the various versions of this API are defined in
versioned client gems, with names of the form google-cloud-oracle_database-v*
.
The gem google-cloud-oracle_database
is the main client library that brings the
verisoned gems in as dependencies, and provides high-level methods for
constructing clients. More information on versioned clients can be found below
in the section titled Which client should I use?.
View the Client Library Documentation
for this library, google-cloud-oracle_database, to see the convenience methods for
constructing client objects. Reference documentation for the client objects
themselves can be found in the client library documentation for the versioned
client gems:
google-cloud-oracle_database-v1.
See also the Product Documentation
for more usage information.
Quick Start
$ gem install google-cloud-oracle_database
In order to use this library, you first need to go through the following steps:
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the API.
- {file:AUTHENTICATION.md Set up authentication.}
Supported Ruby Versions
This library is supported on Ruby 2.7+.
Google provides official support for Ruby versions that are actively supported
by Ruby Core—that is, Ruby versions that are either in normal maintenance or
in security maintenance, and not end of life. Older versions of Ruby may
still work, but are unsupported and not recommended. See
https://www.ruby-lang.org/en/downloads/branches/ for details about the Ruby
support schedule.
Which client should I use?
Most modern Ruby client libraries for Google APIs come in two flavors: the main
client library with a name such as google-cloud-oracle_database
,
and lower-level versioned client libraries with names such as
google-cloud-oracle_database-v1
.
In most cases, you should install the main client.
What's the difference between the main client and a versioned client?
A versioned client provides a basic set of data types and client classes for
a single version of a specific service. (That is, for a service with multiple
versions, there might be a separate versioned client for each service version.)
Most versioned clients are written and maintained by a code generator.
The main client is designed to provide you with the recommended client
interfaces for the service. There will be only one main client for any given
service, even a service with multiple versions. The main client includes
factory methods for constructing the client objects we recommend for most
users. In some cases, those will be classes provided by an underlying versioned
client; in other cases, they will be handwritten higher-level client objects
with additional capabilities, convenience methods, or best practices built in.
Generally, the main client will default to a recommended service version,
although in some cases you can override this if you need to talk to a specific
service version.
Why would I want to use the main client?
We recommend that most users install the main client gem for a service. You can
identify this gem as the one without a version in its name, e.g.
google-cloud-oracle_database
.
The main client is recommended because it will embody the best practices for
accessing the service, and may also provide more convenient interfaces or
tighter integration into frameworks and third-party libraries. In addition, the
documentation and samples published by Google will generally demonstrate use of
the main client.
Why would I want to use a versioned client?
You can use a versioned client if you are content with a possibly lower-level
class interface, you explicitly want to avoid features provided by the main
client, or you want to access a specific service version not be covered by the
main client. You can identify versioned client gems because the service version
is part of the name, e.g. google-cloud-oracle_database-v1
.
What about the google-apis- clients?
Client library gems with names that begin with google-apis-
are based on an
older code generation technology. They talk to a REST/JSON backend (whereas
most modern clients talk to a gRPC backend) and they may
not offer the same performance, features, and ease of use provided by more
modern clients.
The google-apis-
clients have wide coverage across Google services, so you
might need to use one if there is no modern client available for the service.
However, if a modern client is available, we generally recommend it over the
older google-apis-
clients.