Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
I am downloading database script through record types data model' generate database script. It gives both create sequence and create table scripts . In the create sequence the sequence structure is TABLE_NAME_sq. The sq value is in lowercase . But if check in the record fileds primary key edit option it's showing in Uppercase like SQ. So which one should I consider when generating scripts for deploy to other environment. The things the application I'm about to deploy in completely new and we use oracle database which I'm not familiar with so I'm confused.
Discussion posts and replies are publicly visible
In Oracle, unless identifiers (table names, sequence names) are enclosed in double quotes, the database treats them as case-insensitive and stores them as UPPERCASE by default.
If your script says CREATE SEQUENCE my_table_sq, Oracle stores it as MY_TABLE_SQ.
When Appian looks at the database, it sees MY_TABLE_SQ and displays it that way in the UI.
The Verdict: The difference between _sq in the script and _SQ in the Record Type UI is usually just a visual representation. They point to the same object.
Run the generated script as-is.Appian scripts use unquoted lowercase (e.g., TABLE_NAME_sq), Oracle uppercases to TABLE_NAME_SQ automatically. No case issues. UI matches the normalized name.
I'm using them inside the double quotes like - drop sequence "data source"."sequencename", and create sequence "data source"."sequencename". Will that cause issue?
If you use double quotes, case matters. This is true for when creating objects and when querying objects.
In these situations, I typically just give it a try.