There is however no description of the “type” values that the sqltype
parameter takes. Now I’m assuming that because of the name change it must
take a different value and I’m assuming it is basically without the
“cf_sql_”, so:
“cf_sql_varchar” becomes “varchar”
“cf_sql_integer” become “integer”
etc…
Would this be correct? Is there a definitive list somewhere?
Whilst looking at the lucee docs for cfqueryparam I noticed that cfsqltype
is marked as deprecated and there is instead a parameter called sqltype:
[…]
Would this be correct? Is there a definitive list somewhere?
It’s demonstrably ironic that this question arose from reading the docs,
rather than being answered by it.
This reinforces my opinion that automatically scripting the docs from the
source code is… deleterious to the challenge it’s trying to address,
really.
I still think the question of Lucee’s CFML documentation is still at the
drawing board stage, not at the “let’s release a website” stage.On Monday, 9 March 2015 21:31:36 UTC, Andrew Dixon wrote:
Without sqltype the values are treated as chars. For date/time parameters,
this leads to problems as ‘{ts: blah}’ (quoted) is not converted to a date
(at least not by MySQL).
The other types can be converted to the proper type from a string. I rarely
use them either, except maybe for booleans.Op dinsdag 10 maart 2015 11:26:59 UTC+1 schreef Mike Henson:
I have stopped using types all together in query parameters on some small
sites. So far, I have not seen any problems, and I am expecting to find
some weirdness someday, but so far no problems. It would be nice to know
exactly how type should be used, or if it is needed at all.
On Monday, March 9, 2015 at 4:31:36 PM UTC-5, Andrew Dixon wrote:
Hi All,
Whilst looking at the lucee docs for cfqueryparam I noticed that
cfsqltype is marked as deprecated and there is instead a parameter called
sqltype:
There is however no description of the “type” values that the sqltype
parameter takes. Now I’m assuming that because of the name change it must
take a different value and I’m assuming it is basically without the
“cf_sql_”, so:
“cf_sql_varchar” becomes “varchar”
“cf_sql_integer” become “integer”
etc…
Would this be correct? Is there a definitive list somewhere?
I have stopped using types all together in query parameters on some small
sites. So far, I have not seen any problems, and I am expecting to find
some weirdness someday, but so far no problems. It would be nice to know
exactly how type should be used, or if it is needed at all.On Monday, March 9, 2015 at 4:31:36 PM UTC-5, Andrew Dixon wrote:
Hi All,
Whilst looking at the lucee docs for cfqueryparam I noticed that cfsqltype
is marked as deprecated and there is instead a parameter called sqltype:
There is however no description of the “type” values that the sqltype
parameter takes. Now I’m assuming that because of the name change it must
take a different value and I’m assuming it is basically without the
“cf_sql_”, so:
“cf_sql_varchar” becomes “varchar”
“cf_sql_integer” become “integer”
etc…
Would this be correct? Is there a definitive list somewhere?
In addition the attributes do not need to be something like cf_sql_integer
etc. they can be: numerical, string, datetime etc…Op maandag 9 maart 2015 22:31:36 UTC+1 schreef Andrew Dixon:
Hi All,
Whilst looking at the lucee docs for cfqueryparam I noticed that cfsqltype
is marked as deprecated and there is instead a parameter called sqltype:
There is however no description of the “type” values that the sqltype
parameter takes. Now I’m assuming that because of the name change it must
take a different value and I’m assuming it is basically without the
“cf_sql_”, so:
“cf_sql_varchar” becomes “varchar”
“cf_sql_integer” become “integer”
etc…
Would this be correct? Is there a definitive list somewhere?
