Recent changes to support-requests

#4 Output possibly changes while arguments remain unchanged in each run

2024-01-07T12:17:02.577000Z

Thanks, Benedikt!

Andrea

#4 Output possibly changes while arguments remain unchanged in each run

2024-01-02T15:53:40.433000Z

status: open --> closed

#4 Output possibly changes while arguments remain unchanged in each run

2024-01-02T15:53:25.029000Z

Fixed in 1.2:
https://sourceforge.net/projects/csv2ldif2/files/csv2ldif2-1.2.tar.gz/download

#4 Output possibly changes while arguments remain unchanged in each run

2023-12-31T13:26:54.358000Z

Benedikt,
in my view giving a specific order to the components in the output shouldn't be required at all. Though I still wonder why there's no fixed and predictable "default order", I mean as a matter of fact the order of the components in the output changes possibly at each run randomly. I can believe no component is missing anyway, though this random behavior suggests the idea of something out of control, and mysterious at the same time - at least for me, since likely I don't know yet all that I should need to know about perl hash tables.
I'd like at least to understand where the random behavior does come from.

Thanks!

Andrea

#4 Output possibly changes while arguments remain unchanged in each run

2023-12-31T11:30:29.459000Z

Hi, investigated;
reason is that the tool saves its data in a perl hash. And they are, by definition, unordered.
So, if this is really important, it might be an option to add the data into a hash using systematic keys (i.e. add a entry counter number to the front of the key) and sort the entries by that.

But again, LDIF itself is not ordered per se, so - is this important to you, so you need this fixed? What is your usecase?

Ref: https://stackoverflow.com/questions/10901084/how-can-i-sort-a-perl-hash-on-values-and-order-the-keys-correspondingly-in-two#10901159

#4 Output possibly changes while arguments remain unchanged in each run

2023-12-29T18:07:49.327000Z

I attach a csv file with just three records.

Thanks!

Andrea

#4 Output possibly changes while arguments remain unchanged in each run

2023-12-28T23:05:31.780000Z

Do you please have test data for me to reproduce?

My gut says, this is related to perls internal array handling.
But that should not matter - LDIF content files are not ordered.

#5 How to add objectClass attributes?

2023-12-28T23:03:55.986000Z

status: open --> closed

#5 How to add objectClass attributes?

2023-12-28T23:03:38.281000Z

Hello,
yes, thats the way to go.
objectClass is threatened like any other attribute, see the readme file or give the -h option.

$ ./csv2ldif2.pl -b cn=test <<LDIF
cn,mail,objectClass,objectClass
Foo Bar,foo.bar@example.com,inetOrgPerson,person
Test Baz,test.baz@example.com,inetOrgPerson,person
LDIF
dn: cn=Foo Bar,cn=test
cn: Foo Bar
mail: foo.bar@example.com
objectClass: inetOrgPerson
objectClass: person

dn: cn=Test Baz,cn=test
cn: Test Baz
mail: test.baz@example.com
objectClass: inetOrgPerson
objectClass: person

How to add objectClass attributes?

2023-12-28T21:14:47.972000Z

Adding as many columns with the header objectClass as needed, each containing fixed values. Is this the only easy way to get the needed attributes?

Thanks in advance!

Andrea