RE: Client API v1.2.3, VaultHistoryQueryRequest().

Dan,

Thanks for the pointer!  I promise to no longer ask questions until I've
searched the support forums thoroughly. ;)

Brian Schkerke
Lead Developer
NETCO, Inc.
http://www.netcotitle.com
(636) 925 8657

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of 
> Dan Schreiber
> Sent: Wednesday, February 18, 2004 8:44 AM
> To: Brian Schkerke; [email protected]
> Subject: RE: [vault-list] Client API v1.2.3, 
> VaultHistoryQueryRequest().
> 
> Check out http://support.sourcegear.com/viewtopic.php?t=118 - 
> there is some code posted there for implementing history queries...
> 
> -Dan
> 
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]]On Behalf Of Brian 
> > Schkerke
> > Sent: Wednesday, February 18, 2004 8:41 AM
> > To: [email protected]
> > Subject: [vault-list] Client API v1.2.3, VaultHistoryQueryRequest().
> >
> >
> > Given:
> >
> > 	VaultHistoryQueryRequest historyQuery = new 
> > VaultHistoryQueryRequest();
> > 	historyQuery.Recursive = true;
> > 	historyQuery.BeginDate = beginDate;
> > 	historyQuery.EndDate = endDate;
> >
> > 	...
> >
> > 	clientInstance.Connection.HistoryBegin(hq, 
> args.HistoryRowLimit, ref 
> > nRowsRetrieved, ref strQryToken);
> > 	VaultHistoryItem[] historyItems = null;
> > 	clientInstance.Connection.HistoryFetch(strQryToken, 0, 
> > nRowsRetrieved-1, ref historyItems);
> > 	clientInstance.Connection.HistoryEnd(strQryToken);
> >
> > Where do I enforce or activate the date limitation?  I've noticed 
> > VaultHistoryQueryRequest.DateFilterMask (uint) and DateFilterType
> > (int) but
> > VaultHistoryQueryRequest isn't documented in the API (I 
> know, I know, 
> > it's not officially supported. :)) so I'm not sure as to how to 
> > proceed with DateFilterMask or DateFilterType.  The SQL 
> that executes 
> > when the history is retrieved doesn't have any indication of 
> > transaction dates or times in it, but that could be because 
> the dates 
> > I'm passing to VaultHistoryQueryRequest aren't getting that far for 
> > some reason.
> >
> > I currently have a client side filter working but for large 
> > repositories that will get bulky and inefficient fast.
> >
> > Thanks.
> >
> > Brian Schkerke
> > Lead Developer
> > NETCO, Inc.
> > http://www.netcotitle.com
> > (636) 925 8657
> >
> >
> > _______________________________________________
> > vault-list mailing list
> > [email protected]
> > http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list
> 
> _______________________________________________
> vault-list mailing list
> [email protected]
> http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list