P: n/a
|
I need to support multiple keyword search, not boolean searchs, just simple
searches, i.e. "marhsall ma". How is this done? Do I send the entire search
string to the Proc? How do I deal with it there? I'm thinking I need to
build the WHERE clause in the code behind and send it to the proc. What do
you think?
Thanks,
David Lozzi | |
Share this Question
P: n/a
|
David,
You can build the where in the code, as you say. I personally prefer doing
this sort of things in stored procedures, if possible. It should perform
better. Pass one string and parse it in the sp.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message
news:eV*************@TK2MSFTNGP15.phx.gbl... I need to support multiple keyword search, not boolean searchs, just
simple searches, i.e. "marhsall ma". How is this done? Do I send the entire
search string to the Proc? How do I deal with it there? I'm thinking I need to build the WHERE clause in the code behind and send it to the proc. What do you think?
Thanks,
David Lozzi
| |
P: n/a
|
How?
"Eliyahu Goldin" <re*************@monarchmed.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... David,
You can build the where in the code, as you say. I personally prefer doing this sort of things in stored procedures, if possible. It should perform better. Pass one string and parse it in the sp.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message news:eV*************@TK2MSFTNGP15.phx.gbl... I need to support multiple keyword search, not boolean searchs, just simple searches, i.e. "marhsall ma". How is this done? Do I send the entire search string to the Proc? How do I deal with it there? I'm thinking I need to build the WHERE clause in the code behind and send it to the proc. What do you think?
Thanks,
David Lozzi
| |
P: n/a
|
How to parse? Using the language you are writing stored procedures in.
Usually it is Transact-SQL and it has a standard set of string functions.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message
news:uF**************@TK2MSFTNGP09.phx.gbl... How?
"Eliyahu Goldin" <re*************@monarchmed.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... David,
You can build the where in the code, as you say. I personally prefer
doing this sort of things in stored procedures, if possible. It should perform better. Pass one string and parse it in the sp.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message news:eV*************@TK2MSFTNGP15.phx.gbl... I need to support multiple keyword search, not boolean searchs, just simple searches, i.e. "marhsall ma". How is this done? Do I send the entire search string to the Proc? How do I deal with it there? I'm thinking I need to build the WHERE clause in the code behind and send it to the proc. What do you think?
Thanks,
David Lozzi
| |
P: n/a
|
I tend to believe, the string maniputaion functions of .NET will be more
efficient and richer than t-sql or pl-sql
"Eliyahu Goldin" wrote: David,
You can build the where in the code, as you say. I personally prefer doing this sort of things in stored procedures, if possible. It should perform better. Pass one string and parse it in the sp.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message news:eV*************@TK2MSFTNGP15.phx.gbl... I need to support multiple keyword search, not boolean searchs, just simple searches, i.e. "marhsall ma". How is this done? Do I send the entire search string to the Proc? How do I deal with it there? I'm thinking I need to build the WHERE clause in the code behind and send it to the proc. What do you think?
Thanks,
David Lozzi
| |
P: n/a
|
Likely. But stored procedures are pre-compiled. And the database server
usually is big and fast.
Eliyahu
"Sreejith Ram" <Sr*********@discussions.microsoft.com> wrote in message
news:EF**********************************@microsof t.com... I tend to believe, the string maniputaion functions of .NET will be more efficient and richer than t-sql or pl-sql
"Eliyahu Goldin" wrote:
David,
You can build the where in the code, as you say. I personally prefer
doing this sort of things in stored procedures, if possible. It should perform better. Pass one string and parse it in the sp.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message news:eV*************@TK2MSFTNGP15.phx.gbl... I need to support multiple keyword search, not boolean searchs, just simple searches, i.e. "marhsall ma". How is this done? Do I send the entire search string to the Proc? How do I deal with it there? I'm thinking I need
to build the WHERE clause in the code behind and send it to the proc.
What do you think?
Thanks,
David Lozzi
| |
P: n/a
|
Not to argue, just trying to express my understanding...
it is the same case if I build the query in code behind too.. code behind
is compiled (to IL) and big websites run on webfarm, but database servers are
usually just 1 or 2..
building the query dynamically in .NET also helps to make debugging easier
thanks
Sreejith
"Eliyahu Goldin" wrote: Likely. But stored procedures are pre-compiled. And the database server usually is big and fast.
Eliyahu
"Sreejith Ram" <Sr*********@discussions.microsoft.com> wrote in message news:EF**********************************@microsof t.com... I tend to believe, the string maniputaion functions of .NET will be more efficient and richer than t-sql or pl-sql
"Eliyahu Goldin" wrote:
David,
You can build the where in the code, as you say. I personally prefer doing this sort of things in stored procedures, if possible. It should perform better. Pass one string and parse it in the sp.
Eliyahu
"David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message news:eV*************@TK2MSFTNGP15.phx.gbl... > I need to support multiple keyword search, not boolean searchs, just simple > searches, i.e. "marhsall ma". How is this done? Do I send the entire search > string to the Proc? How do I deal with it there? I'm thinking I need to > build the WHERE clause in the code behind and send it to the proc. What do > you think? > > Thanks, > > David Lozzi > > | |
P: n/a
|
I mean stored procedures are pre-compiled on the database server. That makes
the database call faster.
Eliyahu
"Sreejith Ram" <Sr*********@discussions.microsoft.com> wrote in message
news:00**********************************@microsof t.com... Not to argue, just trying to express my understanding...
it is the same case if I build the query in code behind too.. code
behind is compiled (to IL) and big websites run on webfarm, but database servers
are usually just 1 or 2..
building the query dynamically in .NET also helps to make debugging
easier thanks Sreejith
"Eliyahu Goldin" wrote:
Likely. But stored procedures are pre-compiled. And the database server usually is big and fast.
Eliyahu
"Sreejith Ram" <Sr*********@discussions.microsoft.com> wrote in message news:EF**********************************@microsof t.com... I tend to believe, the string maniputaion functions of .NET will be
more efficient and richer than t-sql or pl-sql
"Eliyahu Goldin" wrote:
> David, > > You can build the where in the code, as you say. I personally prefer doing > this sort of things in stored procedures, if possible. It should
perform > better. Pass one string and parse it in the sp. > > Eliyahu > > "David Lozzi" <dlozzi@(removethis)delphi-ts.com> wrote in message > news:eV*************@TK2MSFTNGP15.phx.gbl... > > I need to support multiple keyword search, not boolean searchs,
just > simple > > searches, i.e. "marhsall ma". How is this done? Do I send the
entire > search > > string to the Proc? How do I deal with it there? I'm thinking I
need to > > build the WHERE clause in the code behind and send it to the proc. What do > > you think? > > > > Thanks, > > > > David Lozzi > > > > > > > | | This discussion thread is closed Replies have been disabled for this discussion. | | Question stats - viewed: 1949
- replies: 7
- date asked: Nov 19 '05
|