GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Expectation result: remove 4K truncation · utPLSQL/utPLSQL · Discussion #1375

Expectation result: remove 4K truncation #1375

Unanswered
jgebal asked this question in Feature Requests
Expectation result: remove 4K truncation #1375
@jgebal jgebal
Jul 18, 2026 · 0 comments
Return to top
Discussion options
  • Uh oh!

    There was an error while loading. Please reload this page.

jgebal
Jul 18, 2026
Maintainer

Problem or motivation

The reporter output is now capped at returning 4k chars per one line which affects readability and usability of the data comparison.
Mostly affected are the cursor, object, collection as well as clob and varchar comparison.

Proposed solution

Change how data is collected through expectations and how it is spilled out via reporters to allow for splitting of data that is more than 4k chars per line so that more of the diff data can be shown.

Alternatives or workarounds considered

No response

Framework area

Reporters

utPLSQL version you are using

No response

You must be logged in to vote
All reactions

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
💡
Feature Requests
Labels
None yet
1 participant
@jgebal
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.