This falls under the category of "It's an issue." I'm not joking here.
coCreate has an option, which defaults to true, to throw an error on
unknown properties, so, if you want, you CAN create an object w/
unregistered properties.
My feeling is that if you are creating obs, and making props on the fly,
which could result in unknown props, you should do:
<CFTRY>
make it
<CFCATCH>
delete the ob, or perhaps start a PLP edit to fix it
etc
Just my two cents.
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
> -----Original Message-----
> From: Michiel Boland [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 25, 2001 9:14 AM
> To: Spectra-Talk
> Subject: bug in cfa_contentobjectcreate
>
>
> Hi.
>
> Suppose you create an object like this
>
> <cfset z = StructNew()>
> <cfset z.foo = "bar">
> <cfa_contentobjectcreate
> datasource=...
> typeid=...
> objectid=...
> stProperties="#z#"
> >
>
> Now suppose further that the type of object you are creating
> does not have a property 'foo'. Then the create throws a
> property not registered error. But as a side effect it still
> also creates an object in the database.
>
> IMHO if contentobjectcreate fails for some reason the
> database insert should be rolled back.
>
> Cheers
> Michiel
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
