|
Listbox contains expanders and each of them has different size. The problem is not growing. The problem is to shrink listbox after collapsing expander.
|
|
|
|
|
Hi,
I make a registration form but I have problem when 20 members register in the SAME TIME , what is the best strategy to handle this problem with inserting row in the same time using ado 2.0 and example if available.
|
|
|
|
|
Honeyboy_20 wrote: I have problem
What are the symptoms? What database? What sort of client (Web, WinForms, etc.)?
|
|
|
|
|
What is your problem? Is it timeout or is it concurrency or is it something else? We don't do mind-reading here and we'll not be able to help you unless you are specific about your problem.
|
|
|
|
|
IMO, you don't have too much of an issue while doing an insert. An update or delete can create more issues in terms of concurrency.
However, you can run a check on all existing users to probably check if the user does not already exist.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
|
Are you using the time as some sort of key? If so, don't. Either use an auto_increment column or a GUID as a key so it doesn't matter if you get two entries within the resolution of the timer.
|
|
|
|
|
As you can see from the responses you have gathered here, people are having a real problem understanding what the issue you are suffering really is. As a hint, when posting a question, try to put in as much relevant detail as you can. A description of what you are trying to achieve, along with a relevant code snippet, details of your expected output and a description of the error will help you get a detailed answer to your problem.
If you could edit your question to include this information, I look forward to helping you.
|
|
|
|
|
|
in the end it is not a problem. A database will handle each insert seperately so it will not add two or more rows at once.
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
I'make asp project but my problems happens when over 20 users register in the same time , i found that only 3 users register in db however all 20 users received message that they made registration successfully.
|
|
|
|
|
do you use statics or some kind?
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
|
is there a try catch around the sqlCommand and is the possible exception caught and stored somewhere? That might give a better indictation
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
i am interesting about your system,it's a useful one with large amount of people?
i think if members aren't concentrated at the same time ,you can delay some seconds to release the charge!
|
|
|
|
|
Hi,
I've a DB in MySql, with a field DATE where i store only dates. When i'm getting this field from DB and put it into DataGridView it adds also default time
for example, if i have 1.1.11 in DB, in DataGridView i see "1.1.11 12:00 AM"
how can i prevent the additional date from being added to the datagridview
the thing here is that the one who has implemented this part didn't define a columns in grid view, but just populated it with the DataTable, like this dataGridStatData.DataContext = table.DefaultView; therefore i cant just edit column style...
|
|
|
|
|
There is no such thing as a Date in .Net, only DateTime. So you will need to set a formatter on that column. You can do so by handling the DataBindingComplete event and looking up the column you want to show only dates (or, if all columns in this table which are DateTime should actually only show dates, by type).
|
|
|
|
|
how to get MAC address from Windows-mobile using C# code ?
thank in advance
|
|
|
|
|
|
|
Waaay too late to the party, my friend  ...
1) Anything Linq related is going to be slower...
2) Linq2Sql is dead... I don't believe MSFT is developing it any further, they are focusing on Entity Framework.
Plenty of ORM frameworks to choose from. Linq2Sql is NOT a good pick. EF, nHibernate, etc. are better choices.
|
|
|
|
|
Linq2Sql is dead indeed, but it has been completed. Theres nothing to be done more. So I cannot consider this as a disadvantage.
EF is much more complex and difficult to use. It also has lots of bugs. Linq2Sql is a perfect choice for smaller applications. What about larger apps? EF is also quite slow. In some scenarios ADO.NET could just be better choice.
NHibernate? It almost doesnt have any sensible documentation, tutorials, showhows. It is the worst possible choice in my opinion.
|
|
|
|
|
It's all rubbish. Roll your own so you know what it's doing.
|
|
|
|
|
Haha. And all this time I was thinking it was the latest and greatest.  Oh well, I will definitely look into alternatives, as mentioned. Thanks! :P
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
Although Entity Framework has replaced Linq2Sql in Microsoft's technology stack, the philosophy behind the APIs remains the same. Whatever you've learned about Linq2Sql will help you in EF.
My observation is that ORMs are a lot more flexible on the data query side than on the data manipulation side. I tried Hibernate/nHibernate, Linq2Sql and EF, and in all cases the data retrieval was impeccable. Writing data back, however, was a different story: all frameworks are great when you modify your data in memory and then write it back, but you must jump through the hoops to implement mass inserts (e.g. table-to-table copies), updates, or deletes. Here is a good link that explains the issue and provides a work-around for Linq2Sql[^]. Good luck!
|
|
|
|
|
LINQ to SQL isn't "dead" dead, it is still being supported (and looks likely to remain so for a while) but no new features are being added. Microsoft is focusing on the Enitiy Framework, so that is worth a squizz and having used LINQ to SQL will help you
It is worth looking at the ADO stuff directly, but only so:
a) You understand the underlying technologies
b) You realise exactly how much the various LINQ database stuff is giving you.
Straight ADO was an (u)necessary pain. It is needed to get the data in and out (and therefore necessary). But then you had to work with the results sets, and they didn't play well in OO land.[^] so you had to write your own ORM or live with the fact you were working with relation data and forego a proper object model, without built-in support this was un unecessary pain.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
