MonoSqlite - Revision history

Justincc at 17:17, 18 July 2014

2014-07-18T17:17:51Z

MakoBot: Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T06:44:00Z

Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

MakoBot: Robot: Cosmetic changes

2012-03-04T03:36:20Z

Robot: Cosmetic changes

MakoBot: Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

2011-06-10T23:11:08Z

Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

Ideia Boa at 22:40, 21 May 2009

2009-05-21T22:40:36Z

Phrearch at 09:32, 22 January 2008

2008-01-22T09:32:02Z

Phrearch at 09:25, 22 January 2008

2008-01-22T09:25:20Z

Krisbfunk at 16:26, 15 January 2008

2008-01-15T16:26:54Z

SeanDague at 12:59, 27 August 2007

2007-08-27T12:59:35Z

SeanDague at 12:55, 27 August 2007

2007-08-27T12:55:11Z

@@ Line 1: / Line 1: @@
 {{Quicklinks}}
 <br />
 This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSimulator. There is a real lack of information out there when trying to do something with these technologies.

@@ Line 3: / Line 3: @@
 <br />
-This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.
+This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSimulator. There is a real lack of information out there when trying to do something with these technologies.
 Note: this document is very raw, and under rapid changes. Excuse the brain dump status at this point, it will evolve into something more readable as time goes on.
@@ Line 59: / Line 59: @@
 == Defining Tables in Advance ==
-After a couple of iterations on the OpenSim database, the following pattern has emerged. It has the advantage of letting you defining data tables in a more abstract way that should be usable across database engines with a little bit of work.
+After a couple of iterations on the OpenSimulator database, the following pattern has emerged. It has the advantage of letting you defining data tables in a more abstract way that should be usable across database engines with a little bit of work.
   DataTable prims = new DataTable("prims");

@@ Line 3: / Line 3: @@
 <br />
-This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim.  There is a real lack of information out there when trying to do something with these technologies.
+This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.
-Note: this document is very raw, and under rapid changes.  Excuse the brain dump status at this point, it will evolve into something more readable as time goes on.
+Note: this document is very raw, and under rapid changes. Excuse the brain dump status at this point, it will evolve into something more readable as time goes on.
 = ADO.NET Overview =
-ADO.NET provides a level of abstraction from embedding SQL statements all through your code (which would be very bad).  This is done by creating a top level set of objects that you can use to manipulate loaded data, as well as a way to connect these top level objects to your actual database.
+ADO.NET provides a level of abstraction from embedding SQL statements all through your code (which would be very bad). This is done by creating a top level set of objects that you can use to manipulate loaded data, as well as a way to connect these top level objects to your actual database.
 * Top Level Types
@@ Line 20: / Line 20: @@
 ** SqliteParameter - an SQL parameter for parametrized queries
-One of the early confusion points in reading any MicroSoft based documentation is that MS has claimed Sql as their vendor prefix for MS SQL Server.  This can cause quite a bit of confusion if you think of Sql as something generic, and don't realize those are all examples specific to MS SQL Server.
+One of the early confusion points in reading any MicroSoft based documentation is that MS has claimed Sql as their vendor prefix for MS SQL Server. This can cause quite a bit of confusion if you think of Sql as something generic, and don't realize those are all examples specific to MS SQL Server.
 == Connecting Top Level Types to the Database ==
@@ Line 31: / Line 31: @@
   da.Fill(ds, "prims");
-The database connection is vendor specific, obviously, as is the SQL statement (less obvious, but there are vendor differences that need to be handled).  DataAdapter is an intermediary which manages pulling things from the database and getting them into the DataSet.  Again, you can understand why this would be vendor specific.
+The database connection is vendor specific, obviously, as is the SQL statement (less obvious, but there are vendor differences that need to be handled). DataAdapter is an intermediary which manages pulling things from the database and getting them into the DataSet. Again, you can understand why this would be vendor specific.
 The Dataset then uses that DataAdapter to fill itself from the dataconnection using the fillcmd we have specified.
@@ Line 41: / Line 41: @@
+  }
-This shows how you would get access to rows in a table.  This is equivalent to the "select * from prims" query that was used to Fill() this table.
+This shows how you would get access to rows in a table. This is equivalent to the "select * from prims" query that was used to Fill() this table.
 == XML for Free ==
-One of the great things about using ADO.NET is that you get an intermediary XML format for free.  Every DataSet has the following methods:
+One of the great things about using ADO.NET is that you get an intermediary XML format for free. Every DataSet has the following methods:
 * GetXml(), GetXmlSchema()
 * WriteXml(), WriteXmlSchema()
 * ReadXml(), ReadXmlSchema()
-Each of these provide a full dump/store/load mechanism for the entire DataSet as an XML document.  This includes all tables stored in the DataSet.  GetXml() can be very useful for debugging.
+Each of these provide a full dump/store/load mechanism for the entire DataSet as an XML document. This includes all tables stored in the DataSet. GetXml() can be very useful for debugging.
 = Creating a more usable DataAdapter =
 == The Short Commings of Fill() ==
-Fill will automatically pull in data, create a DataTable, and build some adhoc schema information on that DataTable.  For Sqlite, this information is woefully lacking, as all columns are mapped to strings, and no key information is loaded as part of it (FillSchema() doesn't do it either, go figure).
+Fill will automatically pull in data, create a DataTable, and build some adhoc schema information on that DataTable. For Sqlite, this information is woefully lacking, as all columns are mapped to strings, and no key information is loaded as part of it (FillSchema() doesn't do it either, go figure).
 I'm lazy, and don't like to repeat myself in code, which makes this even more of an issue, as we'll see once we ge to building update commands.
 == Defining Tables in Advance ==
-After a couple of iterations on the OpenSim database, the following pattern has emerged.  It has the advantage of letting you defining data tables in a more abstract way that should be usable across database engines with a little bit of work.
+After a couple of iterations on the OpenSim database, the following pattern has emerged. It has the advantage of letting you defining data tables in a more abstract way that should be usable across database engines with a little bit of work.
   DataTable prims = new DataTable("prims");
@@ Line 68: / Line 68: @@
   prims.PrimaryKey = new DataColumn[] { prims.Columns["UUID"] };
-This produces a much richer DataTable definition, which includes type information on each column, as well as the primary key encoded in the table.  If we have such a table already defined we can use that information in the ds.Fill() call instead.
+This produces a much richer DataTable definition, which includes type information on each column, as well as the primary key encoded in the table. If we have such a table already defined we can use that information in the ds.Fill() call instead.
   ds.Tables.Add(prims);
@@ Line 78: / Line 78: @@
 = Storing and Loading Objects =
 = Initializing the Database =
 [[Category:Development]]

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Template:Quicklinks}}
+{{Quicklinks}}
 <br />

← Older revision		Revision as of 22:40, 21 May 2009
Line 1:		Line 1:
		+	__NOTOC__
		+	{{Template:Quicklinks}}
		+	<br />
		+
	This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.		This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.

← Older revision		Revision as of 09:32, 22 January 2008
Line 1:		Line 1:
−	~~[[Category:Developers]]~~
	This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.		This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.

← Older revision		Revision as of 09:25, 22 January 2008
Line 1:		Line 1:
		+	[[Category:Developers]]
	This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.		This is an attempted writeup of the methodology used with Mono / SQLite / ADO.NET in OpenSim. There is a real lack of information out there when trying to do something with these technologies.

← Older revision		Revision as of 16:26, 15 January 2008
Line 74:		Line 74:
	= Storing and Loading Objects =		= Storing and Loading Objects =
	= Initializing the Database =		= Initializing the Database =
		+	[[Category:Development]]

← Older revision		Revision as of 12:59, 27 August 2007
Line 71:		Line 71:
	== Building SqliteCommands ==		== Building SqliteCommands ==
	The DataAdapter Fill() method gets		The DataAdapter Fill() method gets
		+
		+	= Storing and Loading Objects =
		+	= Initializing the Database =