[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666415#action_12666415
 ] 

Cheong Chung Onn commented on DIRSTUDIO-448:
--------------------------------------------

Hi Pierre-Arnaud,

Yes, I created a new partition without any index attributes. I too am lazy.. :)

Here's  my  2 cents worth about -  should Client or Server side do the ordering.

1. If the Studio or Client side would to do the  ordering, that would mean all 
clients must implement the same piece of logic over and over again. That may 
cause future support issues.

2. If the Server side do the ordering then what happen if Studio is used 
against other Ldap Servers that does not order an exported entries?

For me now, it does not matter whether  Client or Server do the ordering, 
because the only tool i now use  for Ldap development is Apache DS and Studio 
and sometimes OpenLdap to confirm my  development works on it too.

Actually, we fixed the problem by reordering the ldif entries ourselves 
manually. I thought it would be cool if Studio Ldif Editor has a feature to 
re-order the ldif hierarchy. 

> Apache Studio ldif export
> -------------------------
>
>                 Key: DIRSTUDIO-448
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-448
>             Project: Directory Studio
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>         Environment: Ubuntu 8.10, Java 1.6.0_10-b33, Apache Studio 1.3, 
> Apache DS 1.5.4
>            Reporter: Cheong Chung Onn
>
> I exported a branch of entries to an ldif file using Apache Studio version 
> 1.3 and when i tried to import the this ldif file i got numerous errors. I 
> realized the exported ldif file is not sorted in a parent-child entry entry 
> sequence, hence when i re-import this ldif file - i received errors messages 
> that it can't find a entry. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to