Gambas/libraries/gb.db - Revision history

Woozle: reorganizing as subpages

2013-04-24T20:15:07Z

reorganizing as subpages

← Older revision		Revision as of 20:15, 24 April 2013
Line 1:		Line 1:
	==~~Navigation~~==		==About==
	~~<section begin=navbar />~~{{~~#lst:Gambas reference~~\|~~navbar}}: [[~~gb.db~~]]<section end=navbar />~~		{{l/same\|gb.db}} is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:
	~~==Overview==~~
	~~[[gb.db]]~~ is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:
	* [[PostgreSQL]]		* [[PostgreSQL]]
	* [[MySQL]]		* [[MySQL]]
Line 9:		Line 7:
	Both PostgreSQL and MySql are [[client/server]] databases, which means that the connection is made to a [[server process]].		Both PostgreSQL and MySql are [[client/server]] databases, which means that the connection is made to a [[server process]].

	SQLite is more like a library which provides relational database services within the same process, so there is no server process to connect to. This means that the user may need to include a fully qualified path to the database file if the default is not satisfactory. See the ~~[[gb.db.~~Connection]] class for more information.		SQLite is more like a library which provides relational database services within the same process, so there is no server process to connect to. This means that the user may need to include a fully qualified path to the database file if the default is not satisfactory. See the {{l/sub\|Connection}} class for more information.

	This component creates an intermediate layer between the specific server and your program, so that in theory you can use exactly the same code whatever database backend you decide to use. However, there may be variations between engines unless all of the following conditions are met:		This component creates an intermediate layer between the specific server and your program, so that in theory you can use exactly the same code whatever database backend you decide to use. However, there may be variations between engines unless all of the following conditions are met:
Line 17:		Line 15:
	* You don't use the Exec method (which lets you send SQL request directly to the [[backend]], bypassing the [[abstraction layer]])		* You don't use the Exec method (which lets you send SQL request directly to the [[backend]], bypassing the [[abstraction layer]])
	==Classes==		==Classes==
	* ~~[[Connection (gb.db)~~\|Connection]]		* {{l/sub\|Connection}}
	* ~~[[DB (gb.db)~~\|DB]]		* {{l/sub\|DB}}
	* ~~[[Database (gb.db)~~\|Database]]		* {{l/sub\|Database}}
	* ~~[[Field (gb.db)~~\|Field]]		* {{l/sub\|Field}}
	* ~~[[Index (gb.db)~~\|Index]]		* {{l/sub\|Index}}
	* ~~[[Result (gb.db)~~\|Result]]		* {{l/sub\|Result}}
	* ~~[[ResultField (gb.db)~~\|ResultField]]		* {{l/sub\|ResultField}}
	* ~~[[Table (gb.db)~~\|Table]]		* {{l/sub\|Table}}
	* ~~[[User (gb.db)~~\|User]]		* {{l/sub\|User}}
	===Virtual Classes===		===Virtual Classes===
	* ~~[[.ConnectionDatabases (gb.db)~~\|.ConnectionDatabases]]		* {{l/sub\|.ConnectionDatabases}}
	* ~~[[.ConnectionTables (gb.db)~~\|.ConnectionTables]]		* {{l/sub\|.ConnectionTables}}
	* ~~[[.ConnectionUsers (gb.db)~~\|.ConnectionUsers]]		* {{l/sub\|.ConnectionUsers}}

Woozle: Woozle moved page gb.db to Gambas/libraries/gb.db: reorganizing

2013-04-24T20:06:39Z

Woozle moved page gb.db to Gambas/libraries/gb.db: reorganizing

← Older revision	Revision as of 20:06, 24 April 2013
(No difference)

Woozle: converted navbar to use/provide transclusion

2008-01-10T01:17:37Z

converted navbar to use/provide transclusion

← Older revision		Revision as of 01:17, 10 January 2008
Line 1:		Line 1:
	==Navigation==		==Navigation==
	~~[[computing]]~~: ~~[[software]]: [[programming]]: [[Gambas]]: [[~~Gambas reference\|~~reference]]~~: [[gb.db]]		<section begin=navbar />{{#lst:Gambas reference\|navbar}}: [[gb.db]]<section end=navbar />
	==Overview==		==Overview==
	[[gb.db]] is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:		[[gb.db]] is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:

Woozle: added "reference" to navbar

2006-12-05T22:12:57Z

added "reference" to navbar

← Older revision		Revision as of 22:12, 5 December 2006
Line 1:		Line 1:
	==Navigation==		==Navigation==
	[[computing]]: [[software]]: [[programming]]: [[Gambas]]: [[gb.db]]		[[computing]]: [[software]]: [[programming]]: [[Gambas]]: [[Gambas reference\|reference]]: [[gb.db]]
	==Overview==		==Overview==
	[[gb.db]] is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:		[[gb.db]] is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:

Woozle: /* Classes */ virtual classes

2006-12-05T16:32:07Z

Classes: virtual classes

← Older revision		Revision as of 16:32, 5 December 2006
Line 26:		Line 26:
	* [[Table (gb.db)\|Table]]		* [[Table (gb.db)\|Table]]
	* [[User (gb.db)\|User]]		* [[User (gb.db)\|User]]
			===Virtual Classes===
			* [[.ConnectionDatabases (gb.db)\|.ConnectionDatabases]]
			* [[.ConnectionTables (gb.db)\|.ConnectionTables]]
			* [[.ConnectionUsers (gb.db)\|.ConnectionUsers]]

Woozle at 14:43, 5 December 2006

2006-12-05T14:43:59Z

New page

==Navigation==
[[computing]]: [[software]]: [[programming]]: [[Gambas]]: [[gb.db]]
==Overview==
[[gb.db]] is a [[Gambas]] [[library (programming)|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:
* [[PostgreSQL]]
* [[MySQL]]
* [[SQLite]]

Both PostgreSQL and MySql are [[client/server]] databases, which means that the connection is made to a [[server process]].

SQLite is more like a library which provides relational database services within the same process, so there is no server process to connect to. This means that the user may need to include a fully qualified path to the database file if the default is not satisfactory. See the [[gb.db.Connection]] class for more information.

This component creates an intermediate layer between the specific server and your program, so that in theory you can use exactly the same code whatever database backend you decide to use. However, there may be variations between engines unless all of the following conditions are met:
* You create your database by using the [[Gambas Database Manager]] or within Gambas code via gb.db
* You use the Find, Create and Edit methods
* Use the substitution feature of these methods rather than including parameter values directly within the SQL code
* You don't use the Exec method (which lets you send SQL request directly to the [[backend]], bypassing the [[abstraction layer]])
==Classes==
* [[Connection (gb.db)|Connection]]
* [[DB (gb.db)|DB]]
* [[Database (gb.db)|Database]]
* [[Field (gb.db)|Field]]
* [[Index (gb.db)|Index]]
* [[Result (gb.db)|Result]]
* [[ResultField (gb.db)|ResultField]]
* [[Table (gb.db)|Table]]
* [[User (gb.db)|User]]

← Older revision		Revision as of 20:15, 24 April 2013
Line 1:		Line 1:
	==~~Navigation~~==		==About==
	~~<section begin=navbar />~~{{~~#lst:Gambas reference~~\|~~navbar}}: [[~~gb.db~~]]<section end=navbar />~~		{{l/same\|gb.db}} is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:
	~~==Overview==~~
	~~[[gb.db]]~~ is a [[Gambas]] [[library (programming)\|library]] which provides a [[database]] [[abstraction layer]]. It currently supports the following database [[backend]]s:
	* [[PostgreSQL]]		* [[PostgreSQL]]
	* [[MySQL]]		* [[MySQL]]
Line 9:		Line 7:
	Both PostgreSQL and MySql are [[client/server]] databases, which means that the connection is made to a [[server process]].		Both PostgreSQL and MySql are [[client/server]] databases, which means that the connection is made to a [[server process]].

	SQLite is more like a library which provides relational database services within the same process, so there is no server process to connect to. This means that the user may need to include a fully qualified path to the database file if the default is not satisfactory. See the ~~[[gb.db.~~Connection]] class for more information.		SQLite is more like a library which provides relational database services within the same process, so there is no server process to connect to. This means that the user may need to include a fully qualified path to the database file if the default is not satisfactory. See the {{l/sub\|Connection}} class for more information.

	This component creates an intermediate layer between the specific server and your program, so that in theory you can use exactly the same code whatever database backend you decide to use. However, there may be variations between engines unless all of the following conditions are met:		This component creates an intermediate layer between the specific server and your program, so that in theory you can use exactly the same code whatever database backend you decide to use. However, there may be variations between engines unless all of the following conditions are met:
Line 17:		Line 15:
	* You don't use the Exec method (which lets you send SQL request directly to the [[backend]], bypassing the [[abstraction layer]])		* You don't use the Exec method (which lets you send SQL request directly to the [[backend]], bypassing the [[abstraction layer]])
	==Classes==		==Classes==
	* ~~[[Connection (gb.db)~~\|Connection]]		* {{l/sub\|Connection}}
	* ~~[[DB (gb.db)~~\|DB]]		* {{l/sub\|DB}}
	* ~~[[Database (gb.db)~~\|Database]]		* {{l/sub\|Database}}
	* ~~[[Field (gb.db)~~\|Field]]		* {{l/sub\|Field}}
	* ~~[[Index (gb.db)~~\|Index]]		* {{l/sub\|Index}}
	* ~~[[Result (gb.db)~~\|Result]]		* {{l/sub\|Result}}
	* ~~[[ResultField (gb.db)~~\|ResultField]]		* {{l/sub\|ResultField}}
	* ~~[[Table (gb.db)~~\|Table]]		* {{l/sub\|Table}}
	* ~~[[User (gb.db)~~\|User]]		* {{l/sub\|User}}
	===Virtual Classes===		===Virtual Classes===
	* ~~[[.ConnectionDatabases (gb.db)~~\|.ConnectionDatabases]]		* {{l/sub\|.ConnectionDatabases}}
	* ~~[[.ConnectionTables (gb.db)~~\|.ConnectionTables]]		* {{l/sub\|.ConnectionTables}}
	* ~~[[.ConnectionUsers (gb.db)~~\|.ConnectionUsers]]		* {{l/sub\|.ConnectionUsers}}