Free convert int to varchar in sql query software for linux

Practical Query Analyzer produces HTML reports on the most frequent queries, slowest queries, queries by type (select/insert/update/delete), and more for both PostgreSQL and MySQL log files.

Since MySQL is the most popular SQL server that is used in conjunction with web sites, there was a need for incremental backup utility. ZZEE Active SQL Backup is designed for clients of web hosting companies, and can be useful to system administrators as well.
Main features:
- Can perform *incremental* backup of MySQL database
- Can perform full backup of MySQL database
- Can replicate database
- Can process SQL queries
- Can dump database structure
- Can suggest database changes needed to process incremental backup
- Can send data backed up by email
- Can transfer backed up data by FTP to other computer (if Net::FTP is installed)
- Can compress backed up data
Usage synopsis
Active SQL Backup can do incremental or full backups of MySQL database as often as needed. It is suitable both for the clients of web hosting companies who can not get access to MySQL update logs and for the host administrators. Backup syntax is:
shell> ./zmdb.pl -b
It stores backup files in BACKUP_DIR, specified in user_settings.txt, named like YYYY_MM_DD_hh_mm_ss.sql[.gz]. The backup files consist of series of SQL INSERT statements and may contain DELETE statements. The database scheme is stored in file database_name.create.sql. If gzip is available, then Active SQL Backup automatically uses it to compress stored data. The program can automatically send backed up files by email or upload to the other computer by FTP.
If the system fails, Active SQL Backup can restore the database. Restore syntax for incremental backups is:
shell> ./zmdb.pl -r
If you make full backups, restore syntax is the following:
shell> ./zmdb.pl -e < BACKUP_DIR/database_name.create.sql
shell> ./zmdb.pl -e < BACKUP_DIR/YYYY_MM_DD_hh_mm_ss.sql &
The first line is needed to restore database structure, and the second is the *most recent* data file. You may need to "gunzip" it before supplying to restore.
You can use the program to dump database structure
shell> ./zmdb.pl -s > structure_dump_file
or to process queries. The latter feature is useful if you need to process queries regularly, for example, to update membership status of the users of your online service. The syntax to execute SQL queries is:
shell> ./zmdb.pl -e < some_sql_file
Where format of some_sql_file is the same as with Mysql utility: SQL statements are separated by semicolon. Note that if you pass SELECT queries to Active SQL Backup, then no result will be returned.
Syntax summary is:
zmdb.pl [SINGLE_OPTION]
-a --advice suggest database modifications and tables_config.txt
-b --backup backup database structure and data
-e --execute execute SQL queries [from STDIN]
-h --help print this screen
-r --restore restore database structure and data
-s --structure dump database structure [to STDOUT]

DB_DataContainer is a PEAR compliant database persistence layer and data encapsulation class. A persistence layer can encapsulate the behaviour needed to make objects persistent like for exemple: to load, save and delete objects to and from persistent storage. Currently the only supported persistence mechanisms are relational databases. Database abstraction is provided by PEAR DB.
Data encapsulation is provided by overloaded accessor methods. This means that if you have a property named $foo and you do not write getFoo() and setFoo() methods in the extending class yourself, they will be automatically provided by DB_DataContainer.
As a result of the provided persistence mechanism and data encapsulation DB_DataContainer together with few lines of extra code can be used to implement the Active Record Pattern as described by Martin Fowler:
An object that wraps a row in a database table or view, encapsulates the database access, and adds domain logic on that data.
The class does not use any external configuration files. The extending class itself IS the configuration. All you need to take care about is to have matching propertyname - columname pairs in the class and the database table.
If your database schema changes, for example you add an column foo to the table, all you need to do is to add a property name foo to your class which extends DB_DataContainer. There is no need to rewrite any internal SQL queries.
The class does not provide direct support for JOIN:s or table linking. For extreme cases it is still possible to pass hardcoded SQL queries. This usage is discouraged since it breaks the basic idea of using DB_DataContainer.
Main features:
- Simple API
- Persistence mechanism encapsulation. You only need to call load(), save() or delete(). Note that there are no separate methods for INSERT and UPDATE. save() figures itself out which query to use.
- Overloaded accessor methods for class properties without such methods.
- PEAR DB supported databases as persistence mechanisms (tested with Postgres, MySQL, MSSQL and SQLite).
- Multi-object actions provided by a static getObjects() call.
- Possibility to use hardcoded SQL queries in multi-object actions.
- Regression tests.
- Supports PHP4 and PHP5 (starting from version 1.3.0)
Enhancements:
- This release fixes problems with protected and private data members when using PHP5.

RitmarkFS is an open source filesystem storage engine for MySQL server. Using this engine you can work with filesystem on the server with SQL queries and MySQL server interface.RitmarkFS is also possible to access raw file contents.

RitmarkFS allows you to access common file attributes such as name, extension, path, size.

To start using RitmarkFS storage engine you have to create a special table.

Table name specifies filesystem mount point. I.e all data under that mount point will be accessible by the specified table name. In the examples above these were c:ritmarktest and /home/your_home_dir respectively. For example if you run a query like

SELECT * FROM `c$$ritmarktest`;

the query result will contain records corresponding to all files under c:ritmarktest recursively.

The purpose of this project is to provide a simple, generic GUI database browsing frontend. The tool is a very simple aggregation of the Qt database classes.
The database abstraction is provided by the Qt database drivers. So far, the drivers for PostgreSQL and MySQL have been found to work well.
In principle, there is no reason why ODBC drivers for popular databases such as Oracle, DB2, Informix as well as Firebird and SAP/DB shouldnt work via the Qt ODBC3 abstraction layer.
However, some preliminary tests with these have not been promising. It may be that the only way to get some of these working is to create a native Qt database driver. This is something Ill be looking into much later.
At the moment, it is only possible to build the system on Unix and similar systems. Since Trolltech have released a version of Qt for OSX under the GPL and have announced their intention to do likewise for Win32, it should be possible to provide ports for both of these platforms. For the moment though, I just provide the source.
Main features:
- Tree browser for databases and tables
- Display of table descriptions
- Display of table contents in main window
- Execution of ad-hoc SQL queries in the query tab
- Command line history in the query tab
- Retrieval of database connection details from XML config file
- Retrieval of other configuration parameters from XML config file
- Prompting for connection password
- Addition of new connections via GUI to the running application and the config file
- Display database views with a separate icon
- Create a connection name independent of the database name
- A "Test" button when creating a new connection
- Dynamically generate a list of available drivers
- Configuration via autoconf
- Fixed bug with executing updates/inserts twice
- Refreshing of a DB connection
- Deleting of connections via the GUI
- Editting of connections via the GUI
- Check for the existence of ~/.qtsql
- Creation of skeleton config file
- Auto saving/restoring of history
- Loading of queries
- Saving of results
- Keyboard shortcuts

Be::Query is a Perl module to do a query for a given filesystem.

SYNOPSIS

use Be::Query;
@files = Be::Query::Query($filesystem, $query);

do a Query for a given filesystem

USAGE

@files = Be::Query::Query("/boot", "name=lib*.so");

$filesystem is a path anywhere in the target filesystem; $query is a query construction, of the form attribute op value [connector attribute op value]

Such as (name = fido) || (size >= 500)

Metastorage is a PHP data access object generator compiler tool.
Metastorage is an application that automatically generates code for an Object Oriented API to store, retrieve and manipulate the persistent objects of classes described in a high level data model definition.
Metastorage provides a much more efficient development process for medium or large size applications that store and retrieve data from SQL based databases or other types of storage persistence containers, like XML files, flat file databases or LDAP servers.
When storing objects in SQL databases, Metastorage generated code performs efficient object-relational mapping. Metastorage antecipates static storage optimization decisions at compile time, so applications gain in performance, code size and memory usage by avoiding evaluating static decisions at run time.
Main features:
XML definition format
- Easy to write and understand component definition format in XML
Database schemas
- Automatic generation of (database) schema definition of the persistence container
Automatic generation of all classes
- Generates all the code for the data classes, factory class and (database) schema installation class
Self-contained code
- The generated code is self-contained and does not depend on MetaL or libraries of code that are not supplied
Object Query Language
- Provides an Object Query Language (OQL) to define expressions to filter objects in search queries
No SQL
- All code is generated without the need for the developer to write SQL code manually
Forms
- Generation of classes to create, validate and process Web forms to manage objects of the data classes.
Reports
- Generation of classes to execute queries to retrieve data from many objects to elaborate reports or to execute another kind of bulk processing
UML Diagrams
- Automatic generation of Entity-Relationship graphs in UML of the component class diagram