Tyler G Ham wrote:
I looked in the fourq code, it doesn't look like it supports such a field. I tried adding the auto-increment field to the database table generated by my custom type, but then the COAPI-Type Classes page shows the database discrepency warning.
You can happily ignore the warning. Perhaps we should add a new datatype called "custom" which the COAPI just ignores and you have to manage yourself?
Added this thought to the Perculator: http://bugs.farcrycms.org:8080/browse/FC-111
If I don't list the field as a property of my type, it doesn't look like fourq will return the database column's value when returning the type's properties. But if I list the field as a property of my type, fourq won't deploy the column as an auto increment field.
As a workaround you should nominate the field as a numeric, manually change the database schema and ignore the warning.
Would it make sense to make the field a property of the type, deploy it, THEN (manually) make it auto_increment?
Yep -- that's the best approach i think. -- geoff http://www.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/
