Sql fuction manipulate string dynamically may passing parameter string needs to add any character in string given position

Question

1.00/5 (1 vote)

See more:

i have string ', 11, 22,aa, cc, dd, 77 '

i will pass this string to this function as 1st parameter 2nd parameter would be the position on which i want to insert or add comma or number or alphanumeric character between string.

example ' a, b , c , d ,e ,1 ' is string

Fucntioninsertstring ( ' a, b , c , d ,e ,1 ' , 3, F )

out put would be ' a, b , F c , d ,e ,1 '

What I have tried:

i have create function getting all the values passing in string.

but dynamically if i want check send position at which i want to insert any character.

and output will be updated string.

Posted 10-Aug-18 19:37pm

deeptul

Updated 10-Aug-18 21:19pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2018-08-10T21:20:00

Basically, you are doing the wrong thing.
Don't store CSV data in a single column, it becomes a nightmare to work with, partly because SQL string handling is ... um ... poor^*, but mostly because it;s the wrong way to do it.
When you store CSV data, you prevent SQL from doing what it does best: understanding and manipulating the relationships between data - all you gain is a small amount of "easy insert" ability in your presentation language code.
Instead of doing that, set up a separate table to hold each CSV item separately, with a foreign key back to the original table row. That way, insert, remove, search; they all become a whole load simpler, and the original INSERT, UPDATE, and SELECT operations become only slightly more complex.

* He said, politely