dataset « WordPress.com Tag Feed

why do foreigners talk so stupid?

ch0pstick — Sun, 06 Dec 2009 22:04:18 +0000

Let My Dataset Change Your Mindset : Hans Rosling talks @ TED

See more at gapminder.org

Eureqa and Wine

d. — Fri, 04 Dec 2009 23:57:43 +0000

Eureqa runs fine under Wine Check out the specific page multicore Eureqa Wine & Eureqa under Lin

LDC09 dataset dynamics demo - screencast

woddiscovery — Fri, 04 Dec 2009 11:24:43 +0000

Update: for the dataset dynamics demo developed during the Linked Data Camp Vienna there is now also a screen-cast available (video, slides in PDF):

Editions, price and fonctionnalits: to choose well its version Windows 7

kostland — Thu, 03 Dec 2009 16:19:37 +0000

Editions, price and fonctionnalits: to choose well its version Windows 7 – Actualits – Z

Create Expression in DataSet Class using C#

fjchairul — Thu, 03 Dec 2009 04:22:30 +0000

Most of the Expression is use for calculation of column, aggregate value or even copy other column from other datatable. And most of the sample on the web, show how to create example on the source form. Like for example:

DataSet1.Tables("Table1").Columns("Value1").Expression = "Value1 * 0.5"

This short article will show you how to create the expression on the Data Set class.

1. Create a solution and add 1 Data Set.

2. Create a Data Table inside the Data Set.

Create data column as below;

value1 (System.Int32)
value2 (System.Int32)
sumValue (System.Int32)
avgValue (System.Int32)
isEqual (System.String)

3. Double click on the DataTable, and it will show you the class code for you to fill in the method.

namespace expression { partial class dsExpression { partial class dbExpression1DataTable { } } }

Create one method called setupExpression

namespace expression { partial class dsExpression { partial class dbExpression1DataTable { public void setupExpression() { this.sumValueColumn.Expression = "value1 + value2"; this.avgValueColumn.Expression = "(value1 + value2) / 2"; this.isEqualColumn.Expression = "IIF(value1 = value2,'Yes','No')"; } } } }

4. Add Datagridview on top of the form.

5. Bind the DataGridView with the datatable and add the expression.

private void Form1_Load(object sender, EventArgs e) { BindingSource bsBinding = new BindingSource(); dsExpression dsExp = new dsExpression(); dsExp.dbExpression1.setupExpression(); bsBinding.DataSource = dsExp.dbExpression1; dataGridView1.DataSource = bsBinding; }

6. Run the program, and fill in value1 and value2 column.

by pressing Enter it will calculate the value of the sumValue, avgValue, isEqual Column.

There you go! Happy trying good luck…

ASP.NET: How to read XML Data String to Dataset

Red Souldier — Wed, 02 Dec 2009 13:54:43 +0000

The output of XML String:

<?xml version="1.0" encoding="utf-8" ?>
- <NewDataSet>
- <Table>
 <CONDOM>Durex</CONDOM>
 <SIZE>XL</SIZE>
 <QTY>123</QTY>
 <COLOR>616</COLOR>
 </Table>
 </NewDataSet>

In order to convert from XML to dataset, this is the code:

     Dim MyDS as new Dataset("Table1")
     Dim strReader As StringReader = New StringReader(YourXmlString)
     MyDS.ReadXml(strReader)

Let My Dataset Change Your Mindset : Hans Rosling talks @ TED

ch0pstick — Wed, 02 Dec 2009 01:52:12 +0000

See more at gapminder.org

How To Convert a DataSet into a Class

derekrreynolds — Tue, 01 Dec 2009 21:34:34 +0000

Open the Visual Studio .NET command prompt and browse to the directory where your XSD file exists.
Type the following at the prompt: xsd.exe SchemaName.xsd /DataSet /language:CS, where SchemaName.xsd is the name of your XSD file. In this example, the command line looks like this: xsd.exe Customers.xsd /DataSet /language:CS. For Visual Basic .NET, use /language:VB.
Look for your generated class file. In this sample, a file named Customers.cs will be created.

There are several options and flags for the xsd.exe tool, but the important flag for creating your strongly typed DataSet object is the /DataSet flag. This tells the tool to parse through the XSD file and autogenerate a strongly typed DataSet object for you. A view of the command line looks like this:

C:\>xsd.exe Customers.xsd /DataSet /language:CS Microsoft (R) Xml Schemas/DataTypes support utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.


Writing file 'C:\Customers.cs'.

C:\>

Source

Car Datasets

mohsenam — Mon, 30 Nov 2009 00:00:37 +0000

I am looking for the Car Detection Datasets, especially rear and front ones.
I have found following few

http://lear.inrialpes.fr/data
http://www.vision.ee.ethz.ch/~bleibe/data/datasets.html#cars-rear

They have Side view of Car and Multiview Car dataset also

http://www.vision.caltech.edu/html-files/archive.html
http://vasc.ri.cmu.edu/idb/html/car/

The ones in the 2 and 3 are more good trying to get more datasets, if you have some please send me a link

CRM: Dell will propose the solutions of Salesforce. COM with its PC

kostland — Thu, 26 Nov 2009 12:05:59 +0000

CRM: Dell will propose the solutions of Salesforce. COM with its PC – Actualits – ZDNet.

title

kostland — Tue, 24 Nov 2009 14:07:27 +0000

PC: Acer doubles Dell in the 3rd quarter – Actualits – ZDNet. Fr id=”; talkbackfor

Image Segmentation Dataset

siddahuja — Sun, 22 Nov 2009 00:03:40 +0000

Here is a dataset that i prepared for testing image segmentation algorithms. All images are synthetic of size 128×128 (i.e. 16384 pixels in total) and grayscale.

Trin

(4 classes)

(5 classes)

(3 classes)

Jigsaw

(5 classes)

Snowflake

(5 classes)

Sun

(4 classes)

To download the dataset, please Click Here (13 KB, *.rar format)

title

kostland — Wed, 18 Nov 2009 17:11:37 +0000

News of Diane Greene, ex-CEO of VMware id=”; talkbackform”; >; Your comment You N `

All This Without Somatic Cell Nuclear Transfer

fifthsystemeffect — Tue, 17 Nov 2009 00:00:50 +0000

Terroryzm w Rudzie-Gwizdanowie

Mikołaj Morzy — Sat, 07 Nov 2009 00:58:31 +0000

Kto z Was wie, gdzie mieści się Ruda-Gwizdanów? Do dzisiaj też nie miałem pojęcia. W 1997 roku miał tam miejsce atak terrorystyczny, polegający na odpaleniu ładunków wybuchowych podczas spotkania weteranów. Niestety, Wikipedia milczy o ataku, podobnie jak Google. Więc skąd wiem, że terroryści zawitali do Gwizdanowa?

Od 2001 roku Uniwersytet Stanu Maryland gromadzi informacje o aktach terroryzmu na całym świecie. Niedawno baza danych o szumnej nazwie “Global Terrorism Database” została udostępniona publicznie. Baza zawiera informacje o ponad 80 000 aktach terroryzmu i oferuje możliwość wyszukiwania według regionu, kraju, typu ataku, czasu czy liczby ofiar. Serwis oferuje także kalendarium i proste narzędzia do wizualizacji. Wszystkie dane można uzyskać w surowej postaci po skontaktowaniu się z autorami. Baza danych może być swobodnie wykorzystywana do badań naukowych pod warunkiem zacytowania źródła danych. Wszystkie szczegóły znajdują się na głównej stronie projektu.

A tutaj można sprawdzić akty terroryzmu popełnione w Polsce na przestrzeni ostatnich 30 lat.

Entities and n-tier architecture with Visual Studio

Mario Mendez — Tue, 03 Nov 2009 20:14:01 +0000

(original post)

Entity Framework

With the last version of Visual Studio 2008 libraries were incorporated to add LINQ and EDM (Entity Data Model) as part of the Framework 3.5 , which apparently offered a more specialized model to work entities. In fact both have classes and specializied namespaces in entities. More natural would seem to be working in these new frameworks, since generating and entities maintaining facilities strongly typed were resolved; knowing that uncomfortable work for n-tier is falling into the trap of creating and maintaining manually countless endless classes or data structures and methods for go translating them as they are moved from the database to the presentation layer; especially if handled messages instead of referenced libraries.

Well, LINQ and EDM not are the panacea of promised happiness. Unfortunately they are designed essentially to be applied on a single layer, strongly oriented objects; where the connection to a database context instance is permanently alive in application architectures. In fact, its internal logic points more injected by dynamic sql queries work which is not only inefficient on databases with medium or high weight, but it also disconnected from layered architecture scenario left obsolete or unnecessary already 70 % of its methods or objects; mostly devoted to direct consultations an instantiated context. And if you still want to keep these entities for ease of generation, binding controls and control changes or updates is extremely complicated since the internal state of the entities property is read-only, and is modified for use by the context, so those objects are not a support or reusable resource in offline mode.

Try to adapt this and other aspects of connection and transactional management leads to complement the entities by defining classes, partial or inherits, with properties and methods that becomes to a virtual DataSet. Therefore, the best tool for the time to create strongly typed entities remain datasets; or if you want to suffer a little more, but still preferred by lovers of the coupling by messages, helped by seralizables properties attributed xml-based classes.

(tiny)

title

kostland — Tue, 03 Nov 2009 11:08:56 +0000

Patch Tuesday: 10 corrective measures for Windows, Office and Internet Explorer – Actualits

Azure SQL Services: Una completa aplicación de base de datos en línea

Mario Mendez — Wed, 21 Oct 2009 22:31:37 +0000

bases de datos en la nube

Completando las pruebas de los servicios de SQL Azure en el sitio que implementé hace algunas semanas; debo decir que realmente cumplió con lo prometido, y su programación es trasparente para cualquier desarrollador que haya trabajado anteriormente con .Net y SQL Server. De más está decir que el rendimiento en la fase CTP (esto es, con pocos usuarios y bases de datos pequeñas) es óptimo, por lo que a continuación voy a comentar sobre ciertos aspectos a considerar antes de decidir su adopción.

En línea con mis comentarios anteriores, los servicios de SQL Azure están inicialmente destinados para aplicaciones moderadas, sin grandes ambiciones: esto es dado principalmente a que son servicios de base de datos, y por ahora no se ofrecen modalidades OLAP en la nube con miras a extender las prestaciones integrando Datawarehouse en Azure e incorporando funcionalidades de Inteligencia de Negocios (BI). Por otra parte la migración desde y hacia estas bases de datos está limitada a scripts o servicios de integración (SSIS) externos, lo que puede ser un tópico importante frente a aplicaciones de rápido crecimiento de datos, o intentar migrar una aplicación con varios gigas de información almacenada previamente. En efecto, las herramientas de respaldo (backup o detach) no existen en el contexto de aplicación en la nube.

Para el resto de los casos en que lo anterior no representa una desventaja considerable, los puntos a favor no son pocos:

La administración se reduce prácticamente solo a la asignación de permisos, dado que el rendimiento, replicación, y procedimientos de recuperación son responsabilidad del proveedor; que asegura la continuidad (casi) perfecta del servicio.
Los costos del servicio frente a los de una instalación particular del producto SQL Server, equipos necesarios, personal dedicado e infraestructura física para ofrecer un servicio y performance equivalentes son prácticamente irrisorios. La comparación de la inversión se inclina hacia la conveniencia de este servicio, con una diferencia tipo de entre 5 a 15 años a favor del mismo, según el volumen de datos en juego para igualar costos.
El acceso remoto desde aplicaciones por fuera de la nube tienen un muy buen rendimiento, lo que puede ser ventajoso en ciertos escenarios en que se requiera una base centralizada para aplicaciones cliente que por algún motivo no se deseen subir a los servicios web de Azure. En este caso el firewall propio del SQL Azure protege la base obligando a declarar los accesos permitidos según rangos IP predefinidos.
El crecimiento y actualización del servicio está asegurado por el proveedor, quien realizará las implementaciones (upgrade) a través del tiempo en forma completamente trasparente para las aplicaciones, dejando atrás la posibilidad de obsolescencia del entorno.

Adicionalmente durante las pruebas comprobé el comportamiento de transacciones según la clase SqlTransaction (de la librería System.Data.SqlClient) sin problemas; y luego la de transacciones distribuidas (TransactionScope en System.Transactions) según la versión definitiva en línea actualmente del sitio de pruebas. En este último caso, la documentación declara que no está soportada para el caso que se involucren varias bases de datos y otros recursos (como colas); pero para una sola base de datos en Azure SQL se comporta perfectamente según lo esperado, por lo que el servicio de MS DTC se encuentra habilitado por defecto en Azure. Las operaciones las realicé invocando exclusivamente procedimientos almacenados. En este servicio de SQL el tema del rendimiento comparado entre procedimientos almacenados y ejecución de sql dinámico puede que realmente no sean muy diferentes, pero por temas de seguridad y previendo que a la larga pueda ser un factor de incidencia en retardos recomiendo basarse en procedimientos almacenados. Un factor por el que me inclino por esta práctica es que se elimina la posibilidad de ataques por inyección sql por completo, siendo una preocupación menos a controlar en un proyecto de equipo. Por último, una observación respecto al rendimiento de las consultas y los timeout: como siempre influye la pericia del programador y el evitar caer en la tentación del abuso de los recursos del servicio por suponerlos “infinitos”.

Respecto a los objetos de acceso, por los tipos de conexión admitidos resulta imposible acceder con el EDM (Entity Data Model), aunque por su inconveniencia frente a escenarios desconectados que destaqué oportunamente no lo eché de menos. Por este motivo, aunque las clases LinQ contra SQL sí trabajan perfectamente, utilicé el objeto preferido para trabajo desconectado o en n-capas: el DataSet. Por supuesto que hay que hacer algún rodeo mínimo con el Visual Studio 2008 para facilitar su aplicación, pero su programación es transparente y simplifica notablemente el trabajo de crear entidades y acceso a base de datos.

En definitiva, este es el recurso ideal para complementar las aplicaciones de servicios web de Azure, y le da la profundidad necesaria para enfrentar aplicaciones de estilo comerciales o en los que la integridad de los datos y operaciones sean un punto sensible a la hora de realizar un proyecto. Como siempre los invito a recorrer el sitio de pruebas y comprobar en directo sus funcionalidades.

(tiny)

Updating database using dataset

salviashish — Wed, 21 Oct 2009 11:32:22 +0000

This topic illustrates how to update data in a database using a DataSet. It is important to remember that you can also insert, update, and delete data in a database directly using a SqlCommand.

Once the DataSet is loaded, you can modify the data, and the DataSet will track the changes.

The DataSet can be considered an in-memory cache of data retrieved from a database. The DataSet consists of a collection of tables, relationships, and constraints. In this example we will show how to use the Delete method on the DataSet to Delete rows from the database.The Database values are updated with those from Dataset using Update method of SqlDataAdapter

Below are some simple steps to preform Delete operation on Dataset.

STEP 1 : Fill the Dataset with the data you required and bind it to grid.

STEP 2: To Delete a particular row from dataset we required its DatasetIndex, to know the DatasetIndex we perform the delete operation on Grid’s ItemCommand Event.

If e.CommandName = “Delete” Then
parentset.Tables(0).Rows(e.Item.DataSetIndex).Delete()
End If
dgUser.DataSource = UpdateDatabase(parentset, “OleDb”)
dgUser.DataBind()

STEP 3: Create a new instance of OleDbDataAdapter and pass the required parameters, you can either pass OleDbCommand object or write down the Sql statement alongwith the ConnectionString.

Create a instance of OleDbCommandBuilder, it is used to update the changes from Dataset to Database. The parameter required for OleDbCommandBuilder is OleDbDataAdapter with a SELECT Sql statement. The command builder will automatically generate INSERT,UPDATE & DELETE statements for the table and parameters used in SELECT statement.

Public Function UpdateDatabase(ByRef dataSet As DataSet, ByVal Provider As String) As DataSet
If Provider = “OleDb” Then
Dim dbAdapter As New OleDbDataAdapter(“SELECT Sql Statement”,ConnectionString)
Dim objCommandBldr As New OleDbCommandBuilder(dbAdapter)
dbAdapter.Update(dataSet)
ElseIf Provider = “SQL” Then
Dim sqlAdapter As New SqlDataAdapter(“SELECT Sql Statement”,ConnectionString)
Dim sqlCommandBuilder As New SqlCommandBuilder(sqlAdapter)
sqlAdapter.Update(dataSet)
End If
Return dataSet
End Function

STEP 4: Build & Execute.

Here is the link to download the sample application which will demonstrate the above behavior.

You can also find a detailed explanation of Updating Database using Dataset over here.

Enjoy Coding and Keep Learning

Transform a DataSet to JSON using Json.NET (Part 2)

jensendarren — Mon, 19 Oct 2009 15:28:06 +0000

Here is how to transform a DataSet which contains multiple DataTable and DataRelations, well at least, one way you can do it! See Transform a DataSet to JSON using Json.NET (Part 1) for details on how to transform a single DataTable into JSON using Json.NET.

Note that this is designed to work when loading one root row at a time. For example, if you have a database of people and there were related tables for work experience and work experience details then you would load one person and all their related work experience into the DataSet and then use this solution to convert it into JSON.

The DataSet might be designed as follows:

How a basic person with work experience might look as a DataSet. Note: You do not need to specify any attributes except the primary and foreign keys!

We start with the ConvertDataToJson() method which has the same principal purpose as the example in Part 1 except it calls another method GetRelatedData() to return the JSON. Therefore the ConvertDataToJson() is straightforward and looks as follows:

private string ConvertDataToJson()
{
	JObject data =
		new JObject(
				GetRelatedData()
			);
	return data.ToString();
}

The GetRelatedData() method converts the related data into JSON. We first need to calculate the number of related DataTables in the DataSet. That gives us the size we need for our JProperty array. Then, as we loop through each DataTable, we set the name of each JProperty to the name of the DataTable. Note, however, that we check if ds.Tables[i].ParentRelations.Count is greater than 0 before creating a new JArray. This is because we only want to convert the related data into a JArray once and therefore have it be part of a related JSON element once.

If the current table does not have any parent relations we create a JArray and using Linq we enumerate through each row in the table calling ConvertRowToJObject(r) and GetChildRows(r). Here is the complete method:

private JProperty[] GetRelatedData()
{
	//relatedDataArraySize can be passed into this class
	//it is calculated using the following formula
	//relatedDataArraySize = Total number of DataTable - Number of DataTable with DataRelations
	JProperty[] o = new JProperty[relatedDataArraySize];
	int subtractor = 0;
	for (int i = 0; i < ds.Tables.Count; i++)
	{
		if (ds.Tables[i].ParentRelations.Count > 0)
		{
			subtractor += 1;
		}
		if (ds.Tables[i].ParentRelations.Count == 0)
		{
			//Create a JPropery -> JArray
			o[i - subtractor] = new JProperty(ds.Tables[i].TableName,
				new JArray(
					from r in ds.Tables[i].AsEnumerable()
					select new JObject(
						//See Part 1 for an explaination of the ConvertRowToJObject method
						ConvertRowToJObject(r),
						//See below for details of the GetChildRows method
						GetChildRows(r)
					  )));
		}

	}
	return o;
}

In case your interested the code to calculate the relatedDataArraySize is:

foreach (DataTable t in ds.Tables)
{
	if (t.ChildRelations.Count > 0) numberOfTablesWithRelations += 1;
}

The GetChildRows(DataRow) method is as follows. Notice that it is a recursive method so that it will keep calling itself until there are no more child rows for the current DataRow.

private JProperty GetChildRows(DataRow r)
{
	//Hack...need to create a JProperty even if there is no data
	//In your code you might want to remove this element either by a string relpace method
	JProperty o = new JProperty("ignore", "ignore");
	//If there are child rows...
	if (r.Table.ChildRelations.Count > 0)
	{
		if (r.GetChildRows(r.Table.ChildRelations[0]).Length > 0)
		{
			o = new JProperty(r.Table.ChildRelations[0].ChildTable.TableName,
					  new JArray(
					  from rc in r.GetChildRows(r.Table.ChildRelations[0])
					  select new JObject(
						  ConvertRowToJObject(rc),
						  GetChildRows(rc)
			  )));
		}
	}
	return o;
}

Google-like site search in Visual Basic

loganyoung — Thu, 15 Oct 2009 07:17:02 +0000

For a long time, I wondered how to organise a search feature on my site. I could never figure it out

SQL & the JOIN Operator - SQLServerCentral

Visitor Blogs — Sat, 10 Oct 2009 16:45:19 +0000

The Inner Join

This is the most common join we use in SQL. It returns the intersection of two sets. Or in terms of tables, it brings only the records from both tables that match a given criteria.

The FULL JOIN

This is also known as the FULL OUTER JOIN (the reserved word OUTER is optional). FULL JOINs work like the union of two sets.

The LEFT JOIN

Also known as LEFT OUTER JOIN, this is a particular case of the FULL JOIN. It brings all requested data from the table that appears to the left of the JOIN operator, plus the data from the right table which intersects with the first one.

The RIGHT JOIN

Also known as RIGHT OUTER JOIN, this is another particular case of the FULL JOIN. It brings all requested data from the table that appears to the right of the JOIN operator, plus the data from the left table which intersects with the right one.

The CROSS JOIN

A CROSS JOIN is in fact a Cartesian product. Using CROSS JOIN generates exactly the same output of calling two tables (separated by a comma) without any JOIN at all. This means we will get a huge result set, where each record of Table1 will be duplicated for each record in Table2. If Table1 has N1 records and Table2 has N2 records, the output will have N1 times N2 records.

The SELF JOIN

The JOIN operator can be used to combine any pair of tables, including combining the table to itself. This is the “self join”. Self joins can use any JOIN operator.

via SQL & the JOIN Operator – SQLServerCentral.

Understanding INNER join in detail – SQLServerCentral.

The objective of this article is dig into detail of how INNER joins produce the result set. The INNER join is the common join type used in many cases. Even though it is used very often I have seen most people are not certain how it produces the result set when changing the join condition.

Migration towards Windows 7: four companies tmoignent

kostland — Sun, 15 Nov 2009 17:13:24 +0000

Migration towards Windows 7: four companies tmoignent – Actualits – ZDNet. Fr Exit Windo

title

kostland — Tue, 10 Nov 2009 14:33:53 +0000

iPhone in company: a choice sduisant malgr certain gaps – Actualits – ZDNet. Fr Plays vi