getting a lot of vehicles sitting around...

[Lanmanfm]

Getting a lot of vehicles sitting around on my clan server. I was thinking about doing a manual export of the object data table and then hanging onto it for a week and using VBA code to compare the World Space on the 2 exports. A lot of manual manipulation and room for error. I was curious if there was a way to add a "last accessed" time stamp to objects so that I could easily look at any that hadn't been accessed in 7 days and then remove them.

 

If not, I will continue with my original plan.

 

I am just getting tired of taking a run through the woods and finding ambulance after ambulance with the tires missing because someone is using it at a safe.

 

Thanks,

Frank

[itsatrap]

ALTER TABLE `character_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

ALTER TABLE `object_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

[BetterDeadThanZed]

 

ALTER TABLE `character_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

ALTER TABLE `object_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

 

 

Can you explain exactly what this does? Does it automatically make it so if someone interacts with a vehicle, the datastamp gets reset to the current datestamp?

[Lanmanfm]

accessing the gear or taking fuel out of a fuel truck didn't reset the time stamp. taking a tire off did. I haven't added it back to me new server yet, but will today.

[itsatrap]

Can you explain exactly what this does? Does it automatically make it so if someone interacts with a vehicle, the datastamp gets reset to the current datestamp?

 

 

add a timestamp in the sql, thats updates each time some is driving or takings parts on the car, i use it alot for my admin panel and cleanup scripts

[BetterDeadThanZed]

 

ALTER TABLE `character_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

ALTER TABLE `object_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

 

 

When I do the first query, I get this message:

 

#1293 - Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause

 

When I do the second query, it works just fine. My character_data has "Datestamp" and "LastLogin".

[Gimmic]

That likely means there's already a field being updated with the timestamp on update. I bet it's datestamp- any time character data is saved it writes the current_timestamp to the datestamp?

[LimpNoodle]

Wondering why there has been no reply? 

 

 

ALTER TABLE `character_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

ALTER TABLE `object_data`
    ADD `lastactive` timestamp on update current_timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP;

 

 

This does not work for me. MY lastactive column of vehicles gets updated every single server restart...

 

So what to do?