Regarding the rules of brand names, we are brought to change the name of our product, initially named "MySQLVIEW", dedicated to the communication between the LabVIEW™ and LabVIEW Real-Time™ environments and a MySQL™ database "The world's most popular open source database" by the Oracle Corporation.
The new name is : SmartSQLVIEW for MySQL™
Similarly, to present a coherent set of toolkits, we also rename our product SQLiteVIEW, dedicated to the communication between the LabVIEW™ environment and a SQLite database, to the following : SmartSQLVIEW for SQLite
We would like to appologize to the Oracle corporation, and thank them for pointing out this error to us, as well as their understanding and tolerance.
We also like to appologise to our clients for the inconvenience, and hope that it clarified the purpose of our software.
En respect des règles d’utilisation des marques, nous sommes amenés à réviser le nom de notre produit initialement appelé « MySQLVIEW », dédié à la communication depuis les environnements LabVIEW™ et LabVIEW Real-Time™, avec une base de données MySQL™ « The world's most popular open source database », de Oracle Corporation.
La nouvelle désignation devient alors : SmartSQLVIEW for MySQL™
Dans le même temps, afin de présenter une famille cohérente de toolkits, notre produit SQLiteVIEW, dédié à la communication depuis les environnements LabVIEW™ avec une base de données SQLite, est également renommé :SmartSQLVIEW for SQLite
Nous prions la Société Oracle Corporation de nous excuser de l’abus temporairement commis et nous la remercions pour les indications qui nous ont été fournies et pour sa tolérance.
Nous prions nos clients de nous excuser pour les désagréments induits par le changement et nous espérons à cette occasion clarifier le champ d’action des logiciels proposés.
Using a database is more and more requested to manage information in your LabVIEW application. Unfortunately, most of client-server solutions are complex to configure and maintain. SQLite is certainly the right solution !
SQLite is a zero-configuration database.
SQLite does not need to be "installed" before using it. There is no "setup" procedure. There is no server to be started, stopped, nor configured. There is no need (with administrator privileges) to create a new database instance or assign permissions to users. SQLite uses no configuration file. Nothing needs to be done to tell the system that SQLite is running. No action is required to recover data access after system crash or power failure. There is nothing to troubleshoot.
SQLite just works !
Other database engines may run great once you get them going. But doing the initial installation and configuration can often be intimidating.
Database is stored in a single cross-platform disk file
A database in SQLite is a single disk file. Furthermore, the file format is cross-platform. A database that is created on one machine can be copied and used on a different machine with a different architecture. SQLite databases are portable across 32-bit and 64-bit machines and between big-endian and little-endian architectures.
The SQLite database file format is also stable. All releases of of SQLite version 3 can read and write database files created by the very first SQLite 3 release (version 3.0.0) going back to 2004-06-18. This is "backwards compatibility". The developers promise to maintain backwards compatibility of the database file format for all future releases of SQLite 3. "Forwards compatibility" means that older releases of SQLite can also read and write databases created by newer releases. SQLite is usually, but not completely forwards compatible.
The stability of the SQLite database file format and the fact that the file format is cross-platform combine to make SQLite database files an excellent choice as an Application File Format.
Implements most of SQL92
Sources are in the public domain
For these reasons and other features, well-known companies choose SQLite :
We believe that General Electric uses SQLite in some product or another because they twice wrote to the SQLite developers requesting the US Export Control Number for SQLite. So presumably GE is using SQLite in something that they are exporting. But nobody (outside of GE) seems to know what that might be.
It is known that Google uses SQLite in their Desktop for Mac, in Google Gears, in the Android cell-phone operating system, and in the Chrome Web Browser. People are suspicious that Google uses SQLite for lots of other things that we do not know about yet. Engineers at Google have made extensive contributions to the full-text search subsystem within SQLite.
McAfee uses SQLite in its antivirus programs. Mentioned here.
It can inferred from traffic on the SQLite mailing list that at least one group within Microsoft is using SQLite in the development of a game program. No word yet if this game has actually been released or if they are still using SQLite.
The popular PHP programming language comes with both SQLite2 and SQLite3 built in.
SQLite comes bundled with the Python programming language since Python 2.5.
The REALbasic programming environment comes bundled with an enhanced version of SQLite that supports AES encryption.
Solaris 10 uses SQLite as the storage format for its Service Management Facility. Thus, Sun has essentially replaced the traditional unix /etc/inittab file with an SQLite database.
SQLite is an integral part of Symbian's operating system commonly found on high-end cellphones.
A representative of Toshiba wrote to the SQLite developers and requested the US Export Control Number for SQLite. We infer from this that Toshiba is exporting something from the US that uses SQLite, but we do not know what that something is.
Why not using SQlite in your own LabVIEW application !