0001162: Node view database query reporting wrong values - PacketFence

Issue History
Date Modified	Username	Field	Change
2011-01-21 17:06	fgaudreault	New Issue
2011-01-21 17:06	fgaudreault	Target Version	=> 2.0.1
2011-01-21 17:19	obilodeau	mtn revision	=> 03a12d56a57618221c4217e0a4b4b4c7accf0396
2011-01-21 17:19	obilodeau	Note Added: 0001831
2011-01-21 17:19	obilodeau	Status	new => resolved
2011-01-21 17:19	obilodeau	Fixed in Version	=> 2.0.1
2011-01-21 17:19	obilodeau	Resolution	open => fixed
2011-01-21 17:19	obilodeau	Assigned To	=> obilodeau
2011-01-21 17:28	obilodeau	Note Added: 0001832
2011-01-21 17:28	obilodeau	Status	resolved => feedback
2011-01-21 17:28	obilodeau	Resolution	fixed => reopened
2011-01-24 17:32	obilodeau	mtn revision	03a12d56a57618221c4217e0a4b4b4c7accf0396 => 367fb3f1a9e7fcd0c86bcd814f1901cfff376ead
2011-01-24 17:32	obilodeau	Note Added: 0001833
2011-01-24 17:32	obilodeau	Status	feedback => resolved
2011-01-24 17:32	obilodeau	Resolution	reopened => fixed
2011-01-26 15:44	obilodeau	Status	resolved => closed

Notes
(0001831) obilodeau (reporter) 2011-01-21 17:19	Instead of the LEFT JOIN were we hoped we would get proper results we are now using a sorted subselect that does the right thing everywhere.

(0001832) obilodeau (reporter) 2011-01-21 17:28	Turns out the fix is no good. The subselect only fetches the absolute last start_time no matter the MAC so it only fits for one MAC and the rest of the rows are empty.

(0001833) obilodeau (reporter) 2011-01-24 17:32	The subselect with a LIMIT 1 only worked for a single record and not the entire node view so it had to be reverted. Any other attempts I made in that direction were either too slow or incorrect. I settled on a solution that involves not always having the last_... information by joining when end_time is null. This makes sure that the locationlog is always accurate at the cost of losing the information on closed entries.

Relationships