[p4] Can I inject something into a changelist?

[Greg Leach]

The file is generated for an application that needs to know the 
filenames/paths of a directory tree that could contain 80,000+ files.  
Scanning that tree via traditional means just takes too long - so we're 
effectively caching it.  We don't have the time to query the perforce 
server (plus, we don't want to integrate source control into this app).

Other solutions we considered was updating the local copy via the NTFS 
change journal or the indexing service.  They just didn't seem that 
beneficial in the effort vs benefit arena.  We also considered our own 
resident taskbar app, but wanted to leave that as a last resort.  We 
want as few points of failure on the users' machines as possible.

-Greg

Matthew Janulewicz wrote:
> I'd be curious about what problem you are trying to solve with this
> special file. Maybe there's another way.
>
> I would lean toward the suggestion of using already-existing Perforce
> data, like Jobs. It would be possible to fire off a submit trigger that
> creates a job and attaches it to the changelist. You can also go back
> and attach other jobs to a changelist or vice versa, effective updating
> metadata about the changelist but not touching the changelist itself.
>
> But again, what is this data used for?
>
>
> -Matt
>  
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
> Sent: Friday, July 20, 2007 7:19 AM
> To: Greg Leach
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Can I inject something into a changelist?
>
> If the trigger tries to submit another file, you may run into a deadlock
> condition. The submit process you're in holds database locks that would
> be necessary for the submit you want to perform. As you note, there is
> also the recursive trigger issue, so your trigger would have to be aware
> that it needs to ignore changes to the particular file in question.
>
> The daemon approach will work. Just be sure to process the changelists
> one-by-one and to also ignore changes to the special file.
>
> Another approach would be to implement a trigger that only allowed a
> submission if the user made the appropriate change to the special file.
> That would keep the special file in the changelist in which the add or
> delete was applied.
>
> Steve
>   




This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.