U can enter only enter those values in table2(Rank) which are present in Primary Key.
This is the fundamental of having a foreign key. If you want to add values other than those in primary key remove the constraint.
I have multiple results for 1 user. In the example I want the results to get to one row, with the final result (True, True, True, True, True).
So the query has to go through all the results and check if the Access Right is True or False. Is one of them is True the result of the column is true.
I tried to use Temp Tables but im stuck Anyone has an idea?
which would be much easier to query (you can join on ID; you can select on right=true, etc), as well as easier to extend when new access numbers become necessary.
Luc Pattyn [Forum Guidelines][My Articles] The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
You can have your column type as XML and SqlDbType[^] enum supports XML type. You can write something like,
using (SqlConnection conn = /* ... */)
using (SqlCommand cmd = new SqlCommand("insert into your_table VALUES(@xml_content)", conn))
cmd.Parameters.Add("@xml_content", SqlDbType.Xml).Value = new SqlXml(reader);
// other code
SqlXml can take a Stream or a XmlReader instance.
For reading data, work with the SqlDataReader.GetSqlXml()[^] method. SqlXml.ReadOuterXml() will give you a string representation of the XML.
Is Xml Good for large databases?
Shoud i use XmlDocument or XmlReader and XmlWriter?
If i chose XmlReader and XmlWriter how would i manage to quickly delete data?
I am developing OpenSource application, that uses plugin based database.
Is it good to connect to remote server(MySQL) using .NET Connector?
I Also thinking of creating server app that will be on server betwen mysql and Client.
Is TCP good protocol or shoud i consider UDP. Currently i am reading about TCP and i am thinking if i should send XML data through TCP.
Does this data need to be encoded (Base64) or encrypted (AES)?
xml is NOT good for large databases, xml is a descriptive platform it is NOT a database. Some have used it for minute data requirements where it may be valid but certainly not for any valume.
This is dependant on winforms/web application (among other things) you do not say.
We use OLEDB (SQL) connections for winforms
The server app is probably a Web Service - there is plenty of articles and samples around for these.
XML vs Binary transport layer is an old and well used argument, you need to do some research to determine which will suit your needs best.
Encryption is dependant on your data sensitivity, general info may not require encryption where authentication almost certainly does.
Last Visit: 31-Dec-99 18:00 Last Update: 13-Jun-21 17:18