8000 chore: make all wallet format case-insensitive by lowercase by MicBun · Pull Request #918 · trufnetwork/node · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: make all wallet format case-insensitive by lowercase #918

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 5, 2025

Conversation

MicBun
Copy link
Member
@MicBun MicBun commented May 5, 2025

Description

Related Problem

resolves: #916

How Has This Been Tested?

image

@MicBun MicBun requested a review from outerlook May 5, 2025 10:55
@MicBun MicBun self-assigned this May 5, 2025
Copy link
pr-time-tracker bot commented May 5, 2025

Time Submission Status

Member Status Time Action Last Update
MicBun ✅ Submitted 4h Update time May 5, 2025, 11:10 AM
@outerlook ❌ Missing - ⚠️ Submit time -

@MicBun MicBun merged commit 326c842 into refactor/node-2.0 May 5, 2025
3 of 6 checks passed
@MicBun MicBun deleted the chore/caseInsensitive branch May 5, 2025 11:13
outerlook added a commit that referenced this pull request May 5, 2025
MicBun pushed a commit that referenced this pull request May 5, 2025
* fix: correct variable assignment in SQL migration script for case-insensitivity (#918)

* feat: enhance historical record retrieval in SQL migrations

This commit introduces logic to return the latest record when both 'from' and 'to' parameters are omitted in the `get_record_primitive`, `get_index_primitive`, and `get_last_record_composed` actions across multiple SQL migration scripts. These changes improve historical consistency in data retrieval, ensuring that the most recent records are accessible when no specific time range is provided.

* feat: enhance SQL migrations with effective base value retrieval

This commit introduces a new action, `internal_get_base_value`, to improve the retrieval of base values in composed queries. It also adds logic to handle maximum integer values in the `get_index_primitive` and `get_last_record_composed` actions, ensuring that closing deltas for open intervals are not emitted. These changes enhance the accuracy and reliability of historical data retrieval in SQL migrations.

* feat: enhance query tests for latest record and index retrieval

This commit adds new test cases to the query test suite, ensuring that when 'from_time' and 'to_time' are omitted, the latest available record, index, and index change are returned. Additionally, it introduces tests for retrieving records and indices based on specific time parameters, improving the coverage and reliability of the query functionality.
@MicBun MicBun linked an issue May 5, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Problem: New architecture wallet format should be case-sensitive
2 participants
0