-
Dec 31st, 2016, 04:12 AM
#41
Re: Database for desktop application
pal, you should be working with parameters. i thought we told you this.
your code should look something like this:
Code:
SQLCommand.commandtext = "Select * from db where dte >= @dt"
SQLCommand.Parameters.AddwithValue("@dt",dt)
(untested, please investigate)
-
Jan 7th, 2017, 12:31 AM
#42
Thread Starter
Fanatic Member
Re: Database for desktop application
Thanks and I will remember that now.
-
Jan 11th, 2017, 09:31 AM
#43
Thread Starter
Fanatic Member
Re: Database for desktop application
Originally Posted by digitalShaman
pal, you should be working with parameters. i thought we told you this.
your code should look something like this:
Code:
SQLCommand.commandtext = "Select * from db where dte >= @dt"
SQLCommand.Parameters.AddwithValue("@dt",dt)
(untested, please investigate)
If I want database to be accessed by either multiple threads in the application or different part of program at same time then do I need to enable connection pooling. Plus what is the benefit of uisng in memory database. I could not understand the documentation.
Thank you
-
Jan 11th, 2017, 10:04 AM
#44
Re: [RESOLVED] Database for desktop application
do I need to enable connection pooling
No... it just happens. It's handled for you by ADO.NET... you don't need to really do anything other than just use ADO.NET.
Which documentation are your referring to?
-tg
-
Jan 11th, 2017, 12:48 PM
#45
Thread Starter
Fanatic Member
Re: [RESOLVED] Database for desktop application
Originally Posted by techgnome
No... it just happens. It's handled for you by ADO.NET... you don't need to really do anything other than just use ADO.NET.
Which documentation are your referring to?
-tg
I am referring to Sqlite documentation. When should i use inmemory db?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|