http://torasql.com/ 2012-05-18T06:54:49+00:00 http://torasql.com/ http://torasql.com/lib/images/favicon.ico text/html 2010-12-24T09:19:26+00:00 http://torasql.com/knowhow:cache?rev=1293182366&do=diff Cache is used to store some database objects in memory/file in order to reduce repetitive queries of database. Currently TOra cache stores following objects: * Object names (used to store information about all objects except synonyms) * All synonyms for each stored object * List of column descriptions for each stored table (in case of packages “columns” represent package functions and procedures) text/html 2010-03-22T16:09:43+00:00 http://torasql.com/knowhow:configuration?rev=1269274183&do=diff Classes * toConfiguration (toconfiguration.h/cpp) – main class used for configuration. It contains setters and getters for main configuration options (which are stored in toConfigurationPrivate object). * toConfigurationPrivate (toconfiguration.h/cpp) – stores all values of configuration values, has functions to load and save configuration data using QSettings. text/html 2010-02-07T15:21:14+00:00 http://torasql.com/knowhow:connections?rev=1265556074&do=diff Description In order to increase stability of TOra - so that it does not freeze if a connection takes too long, or crash if it never returned - connection pooling mechanism was introduced. It means that for one opened TOra there is more than one database session opened. They are reused in different calls to database and time is not wasted to open/close sessions each time main connection is busy and another session is needed. text/html 2010-02-03T21:05:31+00:00 http://torasql.com/knowhow:debugger?rev=1265231131&do=diff Debug tool uses standard oracle DBMS_DEBUG package to control debug sessions. When debugging you have two sessions: * Debug session – main session from which you're controlling all debug operations, checking status, reading and setting values for variables etc. * Target session – separate session running the code being debugged. This session will usually be executed with a lot of suspensions in order to allow operator to step through statements manually, check and set variable values etc.… text/html 2010-11-28T08:04:01+00:00 http://torasql.com/knowhow:documentation?rev=1290931441&do=diff TOra documentation is used for help system and to generate one documentation book (one pdf file). Files Help files are currently held in three places: * /tora/doc/help * /tora/src/help * /tora-htdocs/help “Main” place for help documents is /tora/doc/help. It is here where files should be modified. Second and third place is actually just a symbolic link to the first one. text/html 2012-04-26T13:41:36+00:00 http://torasql.com/knowhow:index?rev=1335447696&do=diff text/html 2010-11-13T15:12:03+00:00 http://torasql.com/knowhow:parser?rev=1289661123&do=diff Note This document is still a “work in progress”! Parser provides following functionality: * Tokenize given code (string) * Parse given statement (group tokens into statements, blocks etc.) * Indent given code (format) Tokenize Tokeniser takes a string as input and then brakes it up into tokens: identifiers, operators etc. text/html 2010-10-08T18:27:12+00:00 http://torasql.com/knowhow:schemabrowser?rev=1286562432&do=diff Main class for schema browser is toBrowser. It is sub-classed from QTabWidget and provides: * all tabs (tables, views, indexes, synonyms etc.) as depicted in picture below. * list of objects on the left side (marked with red) * details of selected object on the right side (marked with blue) text/html 2010-03-21T16:05:46+00:00 http://torasql.com/knowhow:toextract?rev=1269187546&do=diff This document describes what TOra extractor is and how it works. Extractor (defined as class toExtract (files toextract.h/cpp)) is an interface to different databases. To execute different operations on different databases you will be calling extractor functions which will check which connection is currently being used (oracle, mysql etc.) and will call corresponding database specific implementation. text/html 2012-05-10T23:23:08+00:00 http://torasql.com/knowhow:tora3?rev=1336692188&do=diff This page should summarize possible improvements of the next Tora's major release. Database connections The primary goal is to make the main binary independent to 3rd party libraries. Instalation issues are the most common ones reported by users. The idea is to move link time dependency into side libraries(connection providers). Support for each database is split into multiple parts.