PostgreSQL

Pentabarf travel

Here is the start of a query for pulling out travel requirements for conference attendees. SELECT P.last_name, P.first_name, CPT.arrival_from, CPT.arrival_to, CPT.need_accommodation FROM conference_person_travel CPT, conference_person CP, conference C, person P WHERE CPT.need_accommodation AND CPT.conference_person_id = CP.conference_person_id AND P.person_id = CP.person_id AND CP.conference_id = C.conference_id AND C.acronym = ‘BSDCan2015’

Pentabarf travel Read More »

Pentabarf authentication issues

I encountered this situation recently. I had consolidated two logins. One was for 2012, the other for 2011. It’s better to reuse your login from previous years instead of creating a new one each year. Why? It lets the program committee see what you’ve submitted in previous years. They can see your previous acceptances/rejections. That

Pentabarf authentication issues Read More »

Pentabarf travel

Here is the start of a query for pulling out travel requirements for conference attendees. SELECT P.last_name, P.first_name, CPT.arrival_from, CPT.arrival_to, CPT.need_accommodation FROM conference_person_travel CPT, conference_person CP, conference C, person P WHERE CPT.need_accommodation AND CPT.conference_person_id = CP.conference_person_id AND P.person_id = CP.person_id AND CP.conference_id = C.conference_id AND C.acronym = ‘BSDCan2012’

Pentabarf travel Read More »

Pentabarf fix

After a very long effort, this is the solution: CREATE OR REPLACE FUNCTION conflict.conflict_statistics(conference_id integer, OUT conflict_level text, OUT conflicts integer) RETURNS SETOF record LANGUAGE plpgsql AS $function$ #variable_conflict use_variable DECLARE conflict TEXT; conflict_rows INTEGER; BEGIN FOR conflict_level IN SELECT conflict_level.conflict_level FROM conflict.conflict_level WHERE conflict_level.conflict_level ‘silent’ ORDER BY rank LOOP conflicts = 0; FOR conflict

Pentabarf fix Read More »

Scroll to Top