1994 Osijek café shooting

The 1994 Osijek café shooting was a mass shooting that occurred on June 18, 1994 in Osijek, Osijek-Baranja County, Croatia. Borislav Bešlić shot dead four people and wounded eight others.[1][2]

1994 Osijek café shooting
LocationOsijek, Osijek-Baranja County, Croatia
DateJune 18, 1994
Attack type
Mass shooting
WeaponsAutomatic rifle
Deaths4
Injured8
PerpetratorBorislav Bešlić
MotiveAnti-Serb sentiment
Croatian nationalism

Shooting

On the evening of June 18, 1994 in Osijek, Borislav Bešlić returned from the front with an automatic rifle. He went to the café Grafičar, although the owner closed the gate and told everyone that it does not work, because there were two groups of people, one of whom was celebrating the anniversary of graduation, Bešlić climbed through the gate and entered the café. The celebration was in full swing and the musicians played two Serbian songs. These songs angered Bešlić and he started firing. He fired through a closed glass door, went into the middle and continued firing. Then he sat down at the table, put a machine gun and two grenades on it. He was found there by police. Two guests and two waiters were killed and 8 were injured.[3][1][2][4]

Perpetrator

Borislav Bešlić (41) was a member of the 5th Home Guard Regiment Croatia. The commander of his regiment could not explain how he took the weapon with him. Earlier, he set fire to the restaurant "Fruska gora" in Osijek and was convicted for it.[1][2]

gollark: Basically, if I want to run a search it just goes `SELECT * FROM page_tokens WHERE token = 'one token in search query'` or something like that, and it now has a list of pages with the right token, and SQLite can execute this query relatively fast.
gollark: I mean, as far as I can tell there isn't really a faster *and* more storage-efficient way to do search than the inverted-index page_tokens thing.
gollark: ```sqlCREATE TABLE crawl_queue ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, lockTime INTEGER, added INTEGER NOT NULL, referrer TEXT);CREATE TABLE pages ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, rawContent BLOB NOT NULL, rawFormat TEXT NOT NULL, textContent TEXT NOT NULL, updated INTEGER NOT NULL);CREATE TABLE page_tokens ( id INTEGER PRIMARY KEY, page INTEGER NOT NULL REFERENCES pages(id), token TEXT NOT NULL, weight REAL NOT NULL);CREATE TABLE links ( id INTEGER PRIMARY KEY, toURL TEXT NOT NULL, fromURL TEXT NOT NULL, lastSeen INTEGER NOT NULL, UNIQUE (toURL, fromURL))```Here is the database.
gollark: To be fair, the text content field isn't that necessary, as for search it uses the page_tokens table anyway and it can be rebuilt from the HTML if I need it.
gollark: The frequency of every word *must* be stored for quick (O(log n) time or something) search, the raw HTML or at least might be needed if I come up with a better way to weight frequency or something, the links are useful for (future) better search ranking algorithms.

See also

Podvinje cafe shooting

References
  1. "THE BLOODY GRADUATION NIGHT".
  2. "Vietnam Syndrome Draws Blood".
  3. "KRVAVA MATURANTSKA NOC".
  4. "Likvidirao obitelj jer žena nije htjela preseliti na selo?".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.