Skip to content
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

[#341] New r124/ydb341 subtest (tests YottaDB/YottaDB#341) #375

Merged
merged 1 commit into from
Aug 14, 2018

Conversation

nars1
Copy link
Collaborator

@nars1 nars1 commented Aug 14, 2018

No description provided.

@nars1 nars1 self-assigned this Aug 14, 2018
@nars1 nars1 requested a review from estess August 14, 2018 20:20
@nars1 nars1 merged commit bc00302 into YottaDB:master Aug 14, 2018
Copy link
Contributor

@estess estess left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

But what's with the strange indenting that indents some (mostly SETs but not of them) and not others by 2 bytes?

@nars1
Copy link
Collaborator Author

nars1 commented Aug 14, 2018

Sorry. It is tabs vs spaces. Will fix that next time I am in that module.

@nars1 nars1 deleted the epoch branch August 15, 2018 15:55
nars1 pushed a commit that referenced this pull request Jun 9, 2021
…or file paths over 255 characters

This commit adds a v63010/gtm9076 test that checks that the following expected errors show up in the following 3 circumstances where the file path is over 255 characters:

* When GDE attempts to create a global directory file with a path longer than 255 characters, it produces a `FILEPATHTOOLONG` error.
* When MUPIP CREATE attempts to create a database with a path longer than 255 characters, it produces a `FNTRANSERROR` message.
* When MUPIP attempts to create a journal file with a path longer than 255 characters, it produces a `FILEPATHTOOLONG` error.

The `FILEPATHTOOLONG` error was added in V6.3-010 as a replacement for PARBUSFM that now covers those 2 additional circumstances.`FNTRANSERROR` pre-dates V6.3-010 but its message was changed in V6.3-010 and it was not covered by an existing test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants