Feedback
Did this article resolve your question/issue?

   

Article

Getting compiler error 2589 using SERIALIZE-NAME option of DEFINE TEMP-TABLE statement

« Go Back

Information

 
TitleGetting compiler error 2589 using SERIALIZE-NAME option of DEFINE TEMP-TABLE statement
URL Name000051905
Article Number000169263
EnvironmentProduct: OpenEdge
Version: 10.2A
OS: All Supported Platforms
Question/Problem Description

Getting compiler error 2589 using SERIALIZE-NAME option of DEFINE TEMP-TABLE statement

Steps to Reproduce
Clarifying Information
Error MessageUnrecognized field attribute. (2589)
Defect Number
Enhancement Number
Cause

This is expected behavior.   The SERIALIZE-NAME option/attribute was implemented in 10.2B for JSON support.  The error in question was encountered in 10.2A.

Resolution

Upgrade to OpenEdge 10.2B or later.

Workaround
Notes

References to Other Documentation:

OpenEdge Development, Working with JSON, "Reading and Serializing JSON to/from ProDataSets and Temp-tables", ABL Support for JSON

Last Modified Date7/16/2014 9:00 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.