is there anything wrong with doing a query to leave behind what you don't want?
cfquery dbtype=query name=temp
select * from origQofQ
where not #condition#
/cfquery
cfset origQofQ = temp /
On 4/6/06, Steve Onnis [EMAIL PROTECTED] wrote:
Just my opinion, but that UDF is yuk. Imagine
I know this is possible, Just wondering if anyone on the list is doing it?
If you are? how are you doing it? are you using a JDBC connector? if so?
which one?
Cheers
Gareth.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
that is what I went with before the deleteRow functions came inOn 4/10/06, Barry Beattie [EMAIL PROTECTED]
wrote:is there anything wrong with doing a query to leave behind what you don't want?
cfquery dbtype=query name=tempselect * from origQofQwhere not #condition#/cfquerycfset origQofQ = temp
I ask in case of any performance reasons not to do so.
I've left behind (previous project) an important tool/CFC that uses
this leave behind query method in important areas. If I've made a
faux pas in doing so, I'd like to know
On 4/10/06, Andrew Mercer [EMAIL PROTECTED] wrote:
that is
Aren't some of the example DBs connect to access with just the file
path to the Access DB?
Have a look at those and see how they are done.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
cfaussie group.
To post to
you could just do a QofQ WHERE id something
and if you use cfquery name=sameNameAsExistsingQuery, it would be
the same thing
HTH
On 4/7/06, Andrew Mercer [EMAIL PROTECTED] wrote:
doesnt look like you can do a delete in QoQ
On 4/7/06, Andrew Mercer [EMAIL PROTECTED] wrote:
Does
Using ODBC drivers still I believe.
Could be wrong.
Cheers
Gareth.
David Harris wrote:
Aren't some of the example DBs connect to access with just the file
path to the Access DB?
Have a look at those and see how they are done.
--~--~-~--~~~---~--~~
Not really
what I'm after... I guess I want to set the value of 'cgi.auth_user'. I want to
'authenticate' the user, so they don't see the authentication dialog
box.
It's looking
to me that all this authentication is done client-side, so perhaps CF won't help
me in this case.
thanks!
I'm very interested to see if you come up with a solution for this,
we've been looking for something just like this.
Something that I'm still looking into, but it may be possible for the
pdf document to talk to the container page when your using the embedded
approach. So, maybe create a new
how about a slightly different approach? store all the pdfs outside of the webroot. Then when a user logs in, create a symbolic link to the pdf uuid.pdf points to the pdf outside the web root. Then on session close (CF7) delete the sym link.
Then you can use CF based authentication not IIS
Hi,
Can anyone tell me
whether I am right by making the following assumptions;
To make sure
theproper client is talking to our server over **HTTPS** with XML I can do the
following to authenticate them:
- validate their
remote IP (apparently can be spoofed??) to the one we have on
file
-
11 matches
Mail list logo
