to start things from scratch, you can just drop the table and then
redeploy your type.


On Fri, 12 Nov 2004 08:50:24 -0500, David Ross <[EMAIL PROTECTED]> wrote:
> do you have another property named body? Have you previouslt deployed
> this type? I had some trouble at one point when I tried to add an array
> property to an existing type... my solution was to rename the type to
> something else and redeploy the entire thing.
> 
> -Dave
> 
> >>> [EMAIL PROTECTED] 11/11/2004 8:50:52 PM >>>
> 
> 
> I'm not actually able to store anything in the array yet since there
> seems to be a disconnect in actually deploying the type (from the
> perspective of the FC/Admin/COAPI interface.)
> 
> To test things out, I manaully added several rows directly into the
> table that was created and dumped the object that I added them to and
> they show up as elements in the array. So, it looks like FC is putting
> 
> things back together once the data is there.
> 
> I checked the default dmHTML type for reference and two of the
> properties defined there are arrays (aRelatedIDs and aObjectIDs) --
> both
> deployed fine, albeit during install, so I'm not sure where to go from
> 
> here. Whether I choose 'do nothing' or 'deploy array table' I'm still
> presented with the 'CFC properties conflict' messege.
> 
> Andrew Mercer wrote:
> > farCry turns the cfproperties into table fields - so I think the
> > problem might be that there is not datatype in sqlServer that
> matches
> > to array.
> >
> > What are you holding in the array?
> > Can you swap it for something like a list - in which case you could
> > use a type of string.
> >
> >
> > On Thu, 11 Nov 2004 13:48:17 -0600, Phil Truesdale
> > <[EMAIL PROTECTED]> wrote:
> >
> >>In the process of creating a custom type and I'm encountering an
> error
> >>trying to deploy an array table. It seems simple enough, but when I
> >>redeploy the type with the array property something goes wrong. The
> >>table is created (myType_body), but the type continues to tell me
> that
> >>"The following CFC properties conflicts exist"
> >>
> >>This is the line in my CFC. Simple properties can still be added and
> >>deployed.
> >>
> >><cfproperty name="body" type="array" hint="my hint" required="no"
> >>default="">
> >>
> >>I tried adding an array property to a core type as well and the same
> >>thing happens. Any insight would be greatly appreciated. Thanks.
> >>
> >>Current public version of FC. SQL Server 2k.
> >>
> >>Phil
> >>
> >>---
> >>You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
> >>To unsubscribe send a blank email to
> [EMAIL PROTECTED]
> >>Aussie Macromedia Developers: http://lists.daemon.com.au/
> >>
> >
> >
> >
> 
> ---
> You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
> 
> 
> To unsubscribe send a blank email to
> [EMAIL PROTECTED]
> Aussie Macromedia Developers: http://lists.daemon.com.au/
> 
> ---
> You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to [EMAIL PROTECTED]
> Aussie Macromedia Developers: http://lists.daemon.com.au/
>

---
You are currently subscribed to farcry-dev as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to