Tracking problem

[patrick]

Hello, I have created a tracking table in SQL Server 2000 through Servoy, which workd fine. But when I turn on tracking on certain tables, no data is written. What can I do to trace the problem? I have moved the log to its own database, the back into my solution database. Maybe Servoy doesn't like changes to the log after tracking has been turned on? Any help?

Thank you.

[Jan Blok]

Servoy uses the log table in the "log_server" db server , so check if there is a log table in the "log_server" db server.
Note: You can create the log table in the security dialog

[patrick]

yes, I did everything as described. The log table has been created also, but no records are written.

[Jan Blok]

Is "solution login required" enabled in security dialog? we tested on crm and logging/tracking works correctly.

[patrick]

Yes it is. I have started Servoy via the console to see if I get a message and I do:

java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Dis
allowed implicit conversion from data type datetime to data type timestamp, tabl
e 'Spotlight_Log.dbo.log', column 'event_time'. Use the CONVERT function to run
this query.
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Dis
allowed implicit conversion from data type datetime to data type timestamp, tabl
e 'Spotlight_Log.dbo.log', column 'event_time'. Use the CONVERT function to run
this query.

Does this help?

[patrick]

I have done some more research: first I changed the field type for "event_time" from timestamp to datetime. Now, logging works. Then I encountered another problem: if I want to show the "history" of a record I have to match the records primary key to pk_data. But here we have a datatype problem, too. The pk_data column in the log table is created as varchar which is not compatible to regular primary keys used by Servoy. What is the reason for making this column varchar? I changed it to int and everything seems to work fine...

[Jan Blok]

We had already found the timestamp problem on MSSQL and changed the creation of log table (it now uses the driver setting for correct timestamp db notation) is availeble in release 1.2rc4

About the pk_data this must stay a varchar if multiple pks are defined pk_data will contain: pk1_pk2_pk3_pkN

[pavelzver]

I'm having the same problem, but with mysql. I did check the column (event_type) type and it's set to be datetime, and still no record are written to the log database.
I have tried to start the developer with console and it does not print any error messages.

Windows 2003
Servoy Developer 2.2

Thank you,
Pavel

[Jan Blok]

Did you enable tracking for some tables in the security dialog?

[pavelzver]

Yes, i did and the weird thing is it works on some tables and it doesn't work on others.

Thank you,
Pavel

[Jan Blok]

Could you verify if it is really enabled for those tables, because we are unable to reproduce this.

[pavelzver]

Yes it is enabled on three tables, it works only for one of those three. I did try to disable it and then enable it again, but it did not help. I even tried drop the log table and then create it again, did not help either.

Thank you
Pavel

[sebster]

Is this still an issue? There have been changes to tracking since your post. If it is we'd like to track it down (pun intended ).

[patrick]

I will check that out. Is the problem with log entries for new records fixed? There was a problem that pk_data was NULL if the column had a db sequence...

[pavelzver]

We have dropped this feature and we are not going back to it.