Sybase is doing nothing. The case isn't even assigned to someone. 
Thats it: I'm giving up. When there is a new Version of Sybase (I 
think it is 11 at the moment) I'll try again.
Anyway: many many thanks for your help!

Without any feedback from Sybase, there's not much we can do at the 
current state.

Still nothing from sybase. I'm almost about to give up :( They 
obviously don't care about their customers.

...no. Nothing yet :(
I'll check the sybase ticket tomorrow.
If sybase won't answer: Is there any kind of workaround for my problem?

regards

Any update yet?

I've just created a case in the sybase-bugtracker with No. 11561634 
... See what happens next.

I would rather like to avoid that.

If there is a solution, might it be possible to have 2 ODBC-drivers? 
One for Sybase, another for all other ODBC-driven databases?

The problem is that we can't use any of the casts that we already 
apply when using pgsql or mssql. There might be a syntax that works 
for Sybase, but since we have a single driver for ODBC it might break 
other ODBC-driven databases.

Another interesting fact in statment number 2:



When I change this line

(a1.attribute_name = 'owner' AND a1.attribute_value = 'root') OR



to this line

(a1.attribute_name = 'owner' AND a1.attribute_value = 'root') AND



it works! But maybe it won't in certain circumstances, because the 
logic is changed.

Half success!

First problem is solved, but there's another (same) one.

This statement now works:

SELECT c.datatree_id, c.datatree_name FROM horde_datatree c LEFT JOIN 
horde_datatree_attributes a1 ON a1.datatree_id = c.datatree_id LEFT 
JOIN horde_datatree_attributes a2 ON a2.datatree_id = c.datatree_id 
WHERE c.group_uid = 'horde.shares.kronolith' AND (a1.attribute_name = 
'perm_groups' AND a1.attribute_key IN ('1', '2') AND 
(a1.attribute_value & 2) = 2)  AND a2.attribute_name = 'name'  GROUP 
BY c.datatree_id, c.datatree_name, c.datatree_order, 
a2.attribute_value ORDER BY a2.attribute_value ASC



...after I changed the following values (Sybase Database Options):

Blocking = Off

Optimization_Goal = First-Row

Optimization_Level = 0

Optimization_Logging = On

Prefetch = Off



Now the same problem on a even more complex statement. (It can be 
found in the already attached file horde.log) Error code again -157. 
Message 'conversion from "Kalender von root" to unsigned bigint not 
possible'.



SELECT c.datatree_id, c.datatree_name FROM horde_datatree c

LEFT JOIN horde_datatree_attributes a1 ON a1.datatree_id = c.datatree_id

LEFT JOIN horde_datatree_attributes a2 ON a2.datatree_id = c.datatree_id

LEFT JOIN horde_datatree_attributes a3 ON a3.datatree_id = c.datatree_id

WHERE c.group_uid = 'horde.shares.kronolith' AND

(

   (



     (a1.attribute_name = 'owner' AND a1.attribute_value = 'root') OR



     (a1.attribute_name = 'perm_users' AND a1.attribute_key = 'root' 
AND (a1.attribute_value & 2) = 2) OR

     (a1.attribute_name = 'perm_creator' AND (a1.attribute_value & 2) = 2) OR

     (a1.attribute_name = 'perm_default' AND (a1.attribute_value & 2) = 2) OR

     (a1.attribute_name = 'perm_groups' AND a1.attribute_key IN ('1', 
'2') AND (a1.attribute_value & 2) = 2)

   ) AND a2.attribute_name = 'owner' AND a2.attribute_value = 'root')

AND a1.datatree_id = a2.datatree_id AND a3.attribute_name = 'name'



GROUP BY c.datatree_id, c.datatree_name, c.datatree_order, 
a3.attribute_value ORDER BY a3.attribute_value ASC



-------

But when I remove the line

     (a1.attribute_name = 'owner' AND a1.attribute_value = 'root') OR

it runs perfectly!

No

When I get a workaround for that running, I'll post it here!!

At this moment I also don't know what is wrong with sybase. I will try 
several database-settings and report back. Is there any possibility 
for you to do some testing with a Sybase-DB?

It sounds to me as if Sybase is doing some bad query optimization. 
From the error message it looks like it is doing the 
(a1.attribute_value & 2) = 2 comparison on rows where attribute_value 
contains 'Kalender von root'. This is an expected value for rows that 
have attribute_name = 'name'. But we explicitly ask for attribute_name 
= 'perm_groups' in the query *first*. No idea, why it gets the order 
correct without the group_uid part. And I don't know how to tell 
Sybase to get its optimization correctly done either.

I found something interesting! When I change this statement:



SELECT c.datatree_id, c.datatree_name FROM horde_datatree c

LEFT JOIN horde_datatree_attributes a1 ON a1.datatree_id = c.datatree_id

LEFT JOIN horde_datatree_attributes a2 ON a2.datatree_id = c.datatree_id

WHERE (c.group_uid = 'horde.shares.kronolith') AND

  (a1.attribute_name = 'perm_groups' AND a1.attribute_key IN ('1', '2')

AND (a1.attribute_value & 2) = 2) AND a2.attribute_name = 'name'

GROUP BY c.datatree_id, c.datatree_name, c.datatree_order, 
a2.attribute_value ORDER BY a2.attribute_value ASC



to this statement



SELECT c.datatree_id, c.datatree_name FROM horde_datatree c

LEFT JOIN horde_datatree_attributes a1 ON a1.datatree_id = c.datatree_id

LEFT JOIN horde_datatree_attributes a2 ON a2.datatree_id = c.datatree_id

WHERE

  (a1.attribute_name = 'perm_groups' AND a1.attribute_key IN ('1', '2')

AND (a1.attribute_value & 2) = 2) AND a2.attribute_name = 'name'

GROUP BY c.datatree_id, c.datatree_name, c.datatree_order, 
a2.attribute_value ORDER BY a2.attribute_value ASC



the execution works and returns the values:

datatree_id = 2     and    datatree_name = 'root'



if I put "... where (c.group_uid = 'horde.shares.kronolith') AND ..." 
back in, the same error appeares... See attachment 'hordeStatements.JPG'

I guess Sybase has some kind of problem with this part of the sql-statement:

"... AND a1.attribute_key IN ('1', '2') AND (a1.attribute_value & 8) = 
8)  AND a2.attribute_name = 'name' ...".

Because attribute_value is varchar(255) and not an integer sybase 
seems not to refer to the actual VALUE of attribute_value but instead 
to the TYPE of attribute_value. Maybe it needs some explicit 
conversation at this time.

OR (my 2nd guess)

The mapping between attribute_name and attribute_value somehow fails 
and horde (or sybase?) just takes a wrong value from attribute_value.

No, it's not Horde that is converting. The error message comes from 
Sybase. And I don't know either why this conversion would be needed, 
or when Sybase is trying to do the conversion.

That is correct. The values are saved fine. But horde attempts to 
convert the varchar to bigint for some reason and fails. I don't know 
why this conversion is needed, or if it is needed at all. Anyway it 
fails with error: "Umwandeln von Kalender von root auf unsigned bigint 
nicht möglich" [pid 1052 on line 1252 of "\lib\Horde\DataTree\sql.php"]

-> I translated it to english: "Conversion from 'Kalender von root' to 
unsigned bigint not possible"

I'm not sure what you mean with that. Why should attribute_value be 
converted to bigint? The column is a string, and from your screenshot 
it save both string and integer values just fine, like expected.

I created the missing and invalid tables on my own, by analyzing 
horde-error-logs and using the datatree-create statements.



My tables look like this (sql form)



CREATE TABLE "php"."horde_datatree" (

        "datatree_id" integer NOT NULL,

        "group_uid" varchar(255) NOT NULL,

        "user_uid" varchar(255) NOT NULL,

        "datatree_name" varchar(255) NOT NULL,

        "datatree_parents" varchar(255) NOT NULL,

        "datatree_order" integer NULL,

        "datatree_data" varchar(255) NULL,

        "datatree_serialized" smallint NOT NULL DEFAULT 0,

        PRIMARY KEY ( "datatree_id" )

);



CREATE TABLE "php"."horde_datatree_attributes" (

        "datatree_id" integer NOT NULL,

        "attribute_name" varchar(255) NOT NULL,

        "attribute_key" varchar(255) NULL,

        "attribute_value" varchar(255) NULL

);



Table Data visible in attachment. The Problem is attribute_value which 
can not be converted to bigint (because it is a string)

Looks like scripts/sql/create.sybase.sql (on which the groupware 
script is based) is not really up-to-date. The datatree_order column 
is missing and the horde_datatree_attributes is missing completely.

I will, tomorrow when i'm back at work.
I created the tables via 'scripts/sql/groupware.sybase.sql' statement 
and then replaced 'datatree_data TEXT NOT NULL' with 'datatree_data 
VARCHAR(255) NOT NULL' by hand. (Did not help)

Oh, and how did you create them in the first place, since there is no 
MDB2_Driver_odbc?

How do the datatree tables look like? Can you dump the table structures?

Because there isn't any one.

forgot the attachment....

Sybase database with horde groupware v 1.2.4. Database attached via 
ODBC. (Works perfectly)

When using the share method "sql" horde crashes completely because of 
missing MDB2_ODBC driver.

When using the share method "dataTree" (as workaround) horde says 
"HORDE [error] [kronolith] DB Error: unknown error: SELECT 
c.datatree_id, c.datatree_name FROM 
horde_datatree..................Umwandeln von Kalender von root auf 
unsigned bigint nicht möglich]................."

As a result no shared calendars are configurable. Calendars could be 
created, but don't appear in calendar-settings...

I strongly believe, the dataTree issue is a real bug. Please solve it