I need Yoour help:
I want search from table how many users(id_uzy) makes reservation on example this week, next which hours they reserved (godzina[pl] -> hour[en]) and for this hours find all id_urz.
Example:
id_uzy->1->hour(9-10)-->id_urz(2,3,4)
id_uzy->1->hour(10-11)-->id_urz(2,3,4)
id_uzy-...
@Derek
There is no effective difference between the two. Memory that is no longer useful, and remains uncollected is effectively leaked.
That's true from that perspective, but if there is an actual leak that isn't based on properly making references go out of scope appropriately, that's fun...
@JoePhillips Oh, right, the second number confuses it. There's a number after the question number for your user ID, so the system can track who posted a link for the Announcer badge, and it's showing the question that corresponds to that ID instead. That was reported a long time ago, I guess it's not fixed yet
@balpha It's not unique to /q urls though, you can do stackoverflow.com/questions/123456/1 and get question 1 back. Unless you fixed that and it's only messed up for /q now. The bug with /questions was mentioned in here ages ago
It looks like it is fixed for /questions, so I guess it's a separate bug that looks the same
There are a couple of options for that. First, you could hook the RSS feed for a tag up to Twitter via a free service like TwitterFeed. Second you could create a room in chat that follows a tag and get instant updates in the chat room.
FEATURE REQUEST: prevent auto-scrolling when a message toolbar is open. (so, if i'm hovering over star/flag/reply and someone else posts a message, I don't end up flag/star/replying to them on accident)
@Shog9 Yeah, both of them are problematic, because if I'm on a toolbar, and it stops autoscrolling, then I realize it's the previous message I wanted, I'd be rather upset if it jumped.
HOWEVER, if I leave my cursor in the chat area, and it happens to be over a tool bar, that doesn't necessarily imply that I'm meaning to stop scrolling. So you'd be creating a hidden (read: terrifying) feature.
I suspect (but have not attempted to verify) that the autoscroll feature works by simply checking the scroll position - if it's not at the bottom already, it doesn't try to put it there just because a new message was posted
if that's true, then a naive implementation (that simply adds a check for the cursor over a toolbar button and skips out early) would actually work fairly intuitively: if no-one responds during the hover, autoscroll is re-enabled; if anyone does, autoscroll will be disabled until something else scrolls to the end