Using homogenize() after denormalize() results in some rows without row_names

[Kirkman]

Using homogenize() after denormalize() results in some rows without row_names

[Kirkman]

The kludge I'm using to get around this is to add the following immediately after invoking .homogenize():

	table = table._fork(table.rows, row_names='date')

This basically re-creates the table and forces the addition of row_names to all rows.

[jpmckinney]

I think this can be partially solved in the case where the key argument to homogenize is a single column name, but if it is a sequence of names, then it is not clear which value in compare_values to use as the row name. So, absent adding a row_names parameter to homogenize, I do not think it is possible to preserve the names while also correctly setting names for any added rows. So, closing unless anyone needs this feature.

[Kirkman]

Could .homogenize() be set up to add row names set to None?

I have never used row names for anything explicitly in my code. So I don't understand why it's necessary for .denormalize() to automatically generate them, especially if other methods like homogenize will not generate them.

To me, it feels wrong that the sequence of commands I outlined above (denormalize, homogenize, and then order_by) results in an error. I feel like it should work just fine.

[jpmckinney]

Hmm, that's an idea. I'll reopen the issue.

agate lacks a maintainer, so I'm just stepping in to fix some easy issues and close feature requests that will never be resolved.

[jpmckinney]

I found a simple solution similar to #691.