In January 2011, support for SQL Azure was added. Also at the release, the SQL server version was included in the Premium version of Navicat. Navicat for SQL Server was released in November 2010 for the Windows platform and Mac OS X. In April 2010, Navicat Premium began including Navicat for SQLite starting from version 9 to expand the usability of Navicat Premium. Navicat for SQLite was released for Windows and Mac OS X simultaneously in April 2009, and the Linux version soon followed two months later in June of the same year. The Oracle version of Navicat supports most of the latest Oracle objects features including Directory, Tablespace, Synonym, Materialized View, Trigger, Sequence, and Type, etc. In August of the following year they followed up with a version for the Linux Platform. In August 2008 Navicat decided to further continue their product line and branch out into the Oracle community, creating Navicat for Oracle for Windows and Mac. The Linux version of Navicat for PostgreSQL would not be released until 3 years later in August 2009. PremiumSoft continued to expand their Navicat series by releasing Navicat for PostgreSQL for Windows in October 2005 and then for Mac OS X in June 2006. In November 2013, added the support of MariaDB. Subsequently, the company released two additional versions of Navicat for MySQL on the Mac OS X and Linux operating system in June and October 2003 respectively. Officially released in March 2002, the Windows version of Navicat for MySQL became the first product offered to the public by PremiumSoft. It supports Linux platform via bundled Wine. Upon purchase, users are able to select a language for the software from eleven available languages: English, French, German, Spanish, Japanese, Polish, Russian, Portuguese, Korean, Simplified Chinese and Traditional Chinese. Navicat is a cross-platform tool and works on Microsoft Windows, Mac OS X and Linux platforms. In 2008, Navicat for MySQL was the winner of the Hong Kong ICT 2008 Award of the Year, Best Business Grand Award and Best Business (Product) Gold Award. The main target of the initial version was to simplify the management of MySQL installations. Additional options are available toĬontrol the mapping and conversion for specific BSON data types.The initial version of Navicat was developed by Mr. Must specify the convertBsonTypes option when To convert JSON extensions for BSON types into MySQL types, you Used in expressions and indexes, and manipulated by SQL statements The resulting converted data values can be Represent BSON data types, convert them to an identical orĬompatible MySQL representation, and import the data value using Utility can process documents that use JSON extensions to Represented using extensions to the JSON format. The data types used inīSON documents are not all natively supported by JSON, but can be The JSON import utility can process BSON (binary JSON) data types Supplied import file (without the file extension), and the default The default collection name or table name is the name of the The default collection is createdīy calling the createCollection() functionįrom a schema object. Is automatically created by the utility, using a defaultĬollection or table structure. Table or collection does not exist in the specified database, it You can import the JSON documents to an existing table orĬollection or to a new one created for the import. Into the target database, removing the need to use multiple That the supplied JSON documents are well-formed and inserts them Util.importJSON() enables you to import JSONĭocuments from a file (or FIFO special file) or standard input toĪ MySQL Server collection or relational table. 11.2.1 Running the Utility 11.2.2 Importing JSON Documents With the Mysqlsh Command Interface 11.2.3 Importing JSON Documents With the -import Command 11.2.4 Conversions for Representations of BSON Data Types
0 Comments
Leave a Reply. |