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.

Sign up for GitHub

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

Jump to bottom

Mixed column names using cellHTS2 2.8.0 #23

Closed
GoogleCodeExporter opened this issue Jun 10, 2015 · 1 comment
Closed

Mixed column names using cellHTS2 2.8.0 #23

GoogleCodeExporter opened this issue Jun 10, 2015 · 1 comment
Labels
auto-migrated Component-Logic Milestone-Release0.4 OpSys-All Priority-High Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Use column names with A, b, C (in this order)
2. Execute the CellHTS2 node with all of these parameters

What is the expected output? What do you see instead?
Expected:
the columns are in the A, b, C order, with the expected data in each column.
Got:
The columns are in the A, b, C order, though the contents are in (case
sensitive) alphabetically ordered.

Original issue reported on code.google.com by aborgabor on 24 Jun 2009 at 12:20
@GoogleCodeExporter
Copy link
Author

Original comment by aborgabor on 21 Aug 2009 at 9:41

  • Changed state: Fixed
  • Added labels: Milestone-Release0.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Logic Milestone-Release0.4 OpSys-All Priority-High Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter