C# SQLite query string with a parameter placeholder

Question

What is the benefit of using parameter placeholder:

VALUES (?, ?, ?, ?, ?, ?)

instead of:

VALUES ('@uNameParam', '@bNavnParam', '@passwdParam', '@pc_idParam', '@noterParam', '@licens_idParam')

No "benefit" - some database providers just simply don't support the named parameters (@uNameParam) like SQL Server does...... — marc_s
– marc_s, Commented Aug 10, 2014 at 12:23
Named parameters should not be in quotes - See: stackoverflow.com/questions/751172/… — NoChance
– NoChance, Commented Oct 3, 2016 at 10:55

Grant Winney · Accepted Answer · 2014-08-10 12:36:30Z

3

The first is an example of unnamed parameters. When supplying values for those parameters, the order in which you specify values matters, so that it can match parameters with parameter values correctly.

The second is an example of named parameters. You can usually provide values in any order you want, though that's not always the case.

I don't think there's any benefit of one over the other... it just depends on what's supported for your database and the driver you're using. If you can use either, I'd go for the named parameters for readability alone.

answered Aug 10, 2014 at 12:36

Grant Winney

66.6k13 gold badges120 silver badges167 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

NoChance · Accepted Answer · 2016-10-03 10:51:09Z

1

Named parameters allows the developer from being free in the order parameters are added to the parameter collection. The ? approach, in my opinion, is dangerous coding.

answered Oct 3, 2016 at 10:51

NoChance

5,7844 gold badges38 silver badges50 bronze badges

Collectives™ on Stack Overflow

C# SQLite query string with a parameter placeholder

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related