plug
How about calling your Oracle sales rep and asking how they
are doing on a compliant implementation of SQL/PSM?
/plug
I would, but he's too busy frolicking in a swimming pool full of 100-dollar
bills to answer the phone right now.
Dave Watts, CTO, Fig Leaf Software
hey thanks guys. I already implemented a clunkier way, but I'd be interested
in saving Chris' stored procedure until I'm good enough to implement it. I'll
be implementing searches forever into the future. Why wouldn't it work in
Oracle (which is my DB)?
That's unlikely to work in Oracle
daniel kessler wrote:
hey thanks guys. I already implemented a clunkier way, but I'd be interested
in saving Chris' stored procedure until I'm good enough to implement it.
I'll be implementing searches forever into the future. Why wouldn't it work
in Oracle (which is my DB)?
Stored
Thanks for the explanation Jochem. It doesn't sound all that optimistic.
As for the plug, I'll at least add my noise to my System Administrator here on
campus.
Stored procedures are not very portable (yet) between databases.
The SQL standardization committee was late defining a standard
Ahh, you're using Oracle. Yea, it's going to choke on that one. You could
always try porting it. :)
[EMAIL PROTECTED] 07/06/05 12:37AM
That's unlikely to work in Oracle ;-)
On 7/6/05, Chris Terrebonne [EMAIL PROTECTED] wrote:
Daniel,
Included below is a stored procedure that you can use
I have a table that has about 50 columns. I want to be able to
search ALL columns for the string ***.
I can loop through the columnList with a set of LIKE commands, but is
there a way to search all columns without making 50 LIKE commands?
--
Daniel Kessler
Department of Public and Community
I can loop through the columnList with a set of LIKE commands, but is
there a way to search all columns without making 50 LIKE commands?
If you really have to do this, I would say that the database was very poorly
designed
at the first place. However, you could try an SQL expression that would
If you really have to do this, I would say that the database was very poorly
designed
at the first place.
The database was not poorly designed or rather it may be but this request does
not show it.
This is a one-time request to see if any bad data was entered during the
updating process.
This is a one-time request to see if any bad data was entered during
the updating process.
Ah okaaay, excuse me for the bad design ;-)
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to
If it's a 1 time request, I'd say just write the sql.
If it's something that's going to be done regularly, I'd look into
oracle's full text searches. (You're using oracle, right?)
If you want to learn something new, you could probably write some
pl/sql to look up the column names from the data
If it's something that's going to be done regularly, I'd look into
oracle's full text searches. (You're using oracle, right?)
I am.
If you want to be lazy I'd do select * from mytable in a cfquery, then
dump myquery.columnlist, loop through that and and build your like
statements, then use that
Daniel,
Included below is a stored procedure that you can use to search any or all
columns in all tables.
Once you have installed the SP, call it as follows:
exec spDBSearch @value='MySearchString'
You can also specify a specific column, table or datatype. Let me know if you
have any
That's unlikely to work in Oracle ;-)
On 7/6/05, Chris Terrebonne [EMAIL PROTECTED] wrote:
Daniel,
Included below is a stored procedure that you can use to search any or all
columns in all tables.
~|
Find out how CFTicket
13 matches
Mail list logo
