> Same here, my Sybase setup is pretty basic (ie: I didn't touch anything).
My mistake... It turns out that it's mine system that has been modified.
An excerpt from "Sybase ASE Transact SQL User's guide", page 36:
* Note that Adaptive Server�s sensitivity to the case of database
* objects, such as table names, depends on the sort order installed on
* Adaptive Server. You can change case sensitivity for single-byte
* character sets by reconfiguring the Adaptive Server sort order.
And indeed, I changed sort order in my server to be case insensitive.
I would never suspect that it would change SQL sematics... Anyway,
now we know what was happeing, and my apologies for suspecting
that you messed up your server :)
> > > The two other scripts could be run perfectly.
> >
> > > Well, because one of the scripts wouldn't run correctly, I
> > > think the case
> > > is sensitive.
> >
> > Excuse me, but I think you are contradicting yourself here...
> > Colud you please tell me what error messages you get running
> > the scripts?
>
> No, I wasn't contradicting myself; I ran 3 scripts, 2 schemas, and one
> for data input. I had problem with the data input, because of
> the mixed
> case on the column names.
Sorry for that... Now I understand what you meant. default_roles_permissions.sql
needed to be changed, to match the case of column names with the other SQL files.
I have fixed this in CVS already.
> > Anyway, I have no idea what could be causing your problems
> > with the database.
>
> I'd prefer to see it the other way; if the scripts (and the SQL
> accesses in the program) were consistent, then there would be
> no problem.
Yet again, I'm sorry. You are absolutely right - Turbine should be fixed to work
also with case sensitive engines, though "standard" SQL is not case sensitive
to the best of my knowledge.
> It would be nice if it can be fixed; I guess that the first
> time Turbine
> users would like to see what the screens look like on the
> first install,
> and the first screen would be that login screen.
>
> I don't know, if there's some kind of "Hello World" screen,
> that would be
> nice. So that installation would be easier (no database setup).
Good example code is the thing we are missing the most in this project.
There is code to support database-less setup (TurbineNoDBUserPeer) it
needs to be documented and wrapped up in some exaple code.
> Not for me; currently, I can't add new Turbine users. I think
> the problem
> is pretty clear, Turbine couldn't access the tables (the
> columns) due to
> the case-sensitiveness.
Turbine can't access the tables because there are references to
the tables (or columns) using different case than the schemas,
somewhere in there sources.
I browsed through TurbineMapBuilder and the Peer classes
and it seems that they are consistent with the schemas.
Admin screens/actions use Peers model instead direct SQL queries.
This means that either I overlooked something, or Peers/Village SQL
machinery is messing up the case of column names. I have only
vague idea how these work internally, so I'm asking other developers
in another message.
Are you getting any exception stack dumps in your browser/log file?
If so, please send them to the list - they may be very helpful to us.
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
