Re: Q: How can I use a different core.schema with 2.3.x?

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Monday, January 23, 2006 11:08 AM -0500 Mark Swanson 
<mark@ScheduleWorld.com> wrote:

> Quanah recently asked (2.2 vs 2.3):
> > Wow, out of curiosity, if you were going to upgrade, why would you go
> > from one dead release to another?  Why not go all the way to something
> > supported and current?
>
> Personally, I have not been able to get 2.3.x to work because it doesn't
> seem to support changing the core schema definitions. I must do this
> because most of the existing clients that connect to my service don't
> follow the proper format for things like telephoneNumber.
>
> So my options as I understand it are:
> 1. use 2.3.x and no clients can use the service
> 2. use 2.2 and the clients work fine
>
> I truly would like to use 2.3 and hope that I have made a silly config
> error somewhere. Should I be able to replace telephoneNumber in
> core.schema in 2.3.x?
>
> Thank you.

Are these custom clients?  What prevents them from using the 
telephoneNumber attribute?  At the least, it sounds like the clients you 
have querying your service are horribly broken.

--Quanah


--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html