hotfix(memory.database): order error where db query with field id

[baiyutang]

What type of PR is this?

fix:

Check the PR title.

• This PR title match the format: <type>(optional scope): <description>
• The description of this PR title is user-oriented and clear enough for others to understand.
• Add documentation if the current PR requires user awareness at the usage level.

(Optional) Translate the PR title into Chinese.

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en: db query error when the node execute with a order field.
zh(optional): 数据库查询指定排序时可能会报错

(Optional) Which issue(s) this PR fixes:

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull request overview

This PR fixes a database query error that occurs when specifying an order field using a field ID instead of a field name. The issue arose because the order field mapping logic only checked for field names in the fieldNameToPhysical map but didn't handle field IDs.

Changes:

• Added fallback logic to map order field IDs to their physical names when the field is not found in fieldNameToPhysical

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The comment "AlterID" is vague and doesn't clearly explain the purpose of this else clause. Consider a more descriptive comment such as "Check if order.Field is a field ID (AlterID as string) instead of a field name" to clarify that this handles the case where the field is identified by its ID rather than its name.

Suggested change

	// AlterID
	// Check if order.Field is a field ID (AlterID as string) instead of a field name