These tags are gone, and cannot be recreated; they're marked "intrinsic" so as to allow inbound migrations, but cannot be used on questions here.
Please retag or delete the now-untagged questions
surprise: I thought the Refiner badge was a regular occurrence. But now I am only the 10th the get it... Do the others here always answer already perfect questions? ;)
I am using 9.2 PostgreSQL, and I was just playing with configuration files.
The following things I have done:
stopped slave server
renamed recovery.conf to recovery.conf.sample
restarted slave server
Now rsyncing has completely stopped.
After this, I tried restarting slave with recovery.con...
I actually thought it might be better to post it as a separate answer, because it differs substantially. But it's all right. I'll take a look, thanks again.
Sort of related, when I have a column with the type uniqueidentifier, is it always unique to the table, or should I check for duplicates? I realize the chances are miniscule, but I'm curious what's the right thing to do.
In my design each session will always be unique per row. It's possible that the same user may have multiple sessions, but each session will still use a unique key.
@WilliamMariager All alternatives are valid choices in different scenarios. If you don't need an Id (identity?) you don't have to use one. There are issues associated with having a UUID as the primary key, because the default is that primary keys are clustered.
Having a clustering key with a random insert point profile can lead to table fragmentation and inefficient use of space (memory and disk).
While creating a test database for another question I asked earlier, I remembered about a Primary Key being able to be declared NONCLUSTERED
When would you use a NONCLUSTERED primary key as opposed to a CLUSTERED primary key?
Thanks in advance
I've being reading around reasons to use or not Guid and int.
int is smaller, faster, easy to remember, keeps a chronological sequence. And as for Guid, the only advantage I found is that it is unique. In which case a Guid would be better than and int and why?
From what I've seen, int has no fl...
Quick update on the blog thing, @PaulWhite: static pages are a possibility. So the issue of broken links and whatnot you mentioned... well, it wouldn't be an issue any more :)
@WilliamMariager Well everything is a trade off. If you generally fetch rows by UUID, having the PK nonclustered means every fetch requires a lookup to the base table to fetch the non-key columns.
Can circular references cause issues in SQL Server? Lets say I have a User, with a column that points to itself? I would like to have a CreatedBy column on my user table.
Actually I have been reading lately (in the TTM mailing list, which is crowded by hard-core relational-model guys) a discussion about how (D) could be implemented in Javascript
@WilliamMariager What do you mean by "column that points to itself"? That just doesn't make much sense. Did you mean a column that points to another column in the same table?
@PaulWhite On other communities that have chat rooms dedicated to their blog, I know precisely where and who to contact about decisions to the blog. If they feel like a wider range of opinions is needed, they can bring it to the wider community.
In communities with pretty dead blog like yours, my best chance of finding someone who cares about their blogs is reaching out to mods. If you feel you can make an informed decision for the community, cool. If you think opinions from the community as a whole are necessary, I'd recommend starting a Meta post.
@JNat Ok I pinged the others above. I have no time right now, but "nope" I hadn't considered writing a meta post, but I might, just not right now. Cheers.
Quick update on the blog thing, @PaulWhite: static pages are a possibility. So the issue of broken links and whatnot you mentioned... well, it wouldn't be an issue any more :)
:)
We were still evaluating the possibility when I came in here last week
@jcolebrand Ok cool. Then coordinate with Paul and start a Meta post on it. I'll ping you guys in about two weeks or so to find out what conclusions y'all came to :)
@Philᵀᴹ If you migrated to Medium, I know the Worldbuilding community would be willing to help, as they have their blog there
@JNat I thought we could have a productive blog if content creation was familiar to site users and tied to the site, and if people didn't have to have yet another login to provide content — failing that I don't see it working for dba.se on an external blogging platform any more than it did on blogoverflow.
Stack Exchange is going to be discontinuing the BlogOverflow.com website for community blogs.
We could migrate the few posts we had to another blogging platform, or (iiuc) it can just be converted to static pages in situ.
Stack Exchange is going to be discontinuing the BlogOverflow.com website for community blogs.
We could migrate the few posts we had to another blogging platform, or (iiuc) it can just be converted to static pages in situ.
However, our blog is something we hardly ever talk about.
http://dba.blogoverflow.com/2012/06/help-us-help-you/
Have you ever seen this post? Isn't it helpful?
Well, there's this little issue. The resources for BlogOverflow are going to be decommissioned (to some degree) so we have a few o...
However, our blog is something we hardly ever talk about.
http://dba.blogoverflow.com/2012/06/help-us-help-you/
Have you ever seen this post? Isn't it helpful?
Well, there's this little issue. The resources for BlogOverflow are going to be decommissioned (to some degree) so we have a few o...
However, our blog is something we hardly ever talk about.
http://dba.blogoverflow.com/2012/06/help-us-help-you/
Have you ever seen this post? Isn't it helpful?
Well, there's this little issue. The resources for BlogOverflow are going to be decommissioned (to some degree) so we have a few o...
It makes sense to clean up a database from time to time right? I have sessions which are usually only valid for 12 hours. So I was thinking I'd make a task that runs through and removes invalid sessions once per day.
Oh, by sessions I mean I have a Sessions table with rows. The rows each have an expiration datetime column, after which the session is invalid and they're not longer used.
I'm using SQL Server. Not sure what app stack means.
And I'm just trying to remove rows that I know will never be used again from a table.
That's interesting. I'm not sure I'll ever need it, but maybe in the future.
It's not a problem at all, just curious what you'd normally do.
I could store a "LastUsed" datetime which is updated whenever the session is used. This would give me some data on how long users would normally be active.