On 6/26/07, Brian Whitfield / Essential Resources
[EMAIL PROTECTED] wrote:
It is not a measure of how good or bad Coldfusion is. But more a measure of
its popularity as a language.
If my career were dictated by a popularity contest I would be
switching technologies every week... and I would
Usually when working with workspaces, you will have the option to switch
wherever you keep your workspace. By deleting the workspace folder, it will
reset your perspectives and views. You can also switch your workspace to a
previously saved workspace when you really like your settings. The
To add, I suggest reading through the Eclipse tutorials, they speak to this
and other things pretty well. As Teddy said, workspaces are pretty much
what the phrase evokes, a space to work in. This includes settings and
such so you can have say personalized settings for one workspace and a
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas
Knudsen
To add, I suggest reading through the Eclipse tutorials, they speak to
this and other things pretty well.
[Tepfer, Seth] Thanks for the suggestions on the tutorials.
For CF only projects, I keep the project in the
Hi,
some of the Eclipse vs DW vs other IDE discussion has already been done
before. Here is the link :
http://www.mail-archive.com/discussion@acfug.org/msg02117.html
or go to mailbox archive of discussion
http://www.mail-archive.com/discussion@acfug.org/
and search for dw or eclipse. There
I have an sql server database table (tblWebsiteUsers) with 22,000 users in
it. There are some records that have duplicate usernames. I know I can write
some cf code to handle this but I thought maybe one of you SQL server gurus
might be able to provide a slicker way to identify the ones that have
I think I answered my own question ...
_
From: Dusty Hale [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 27, 2007 10:47 AM
To: 'discussion@acfug.org'
Subject: OT - SQL - Finding duplicate usernames
I have an sql server database table (tblWebsiteUsers) with 22,000 users in
it. There
Dusty,
Yeah, it sounded like you saw that creating a new table was a decent idea. I
am a big fan of creating new tables using Select * into tblName and * being
whatever columns you want. Avoid the temp table and don't use cursors wherever
you can. =)
Teddy
- Original Message -
SELECTCOUNT(*), UserName
FROMtblWebsiteUsers
GROUP BY UserName
HAVING COUNT(*) 1
This will give all the usernames that have duplicates. Are you trying to
delete the duplicates or just identify them?
Scott
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Yes actually that is the query I just used. I was trying to just identify
them for now. Turns out there are 1180 users that have one or more
duplicates. Ouch some customer service rep is going to have a fun time
dealing with these users . OR I will make some $ writing some extra code
to
Well, you need to stem the duplicates before creating database solutions.
During the User creation process, there needs to be a duplicate notification
that had a good amount of detail. Obviously, there may be more than one person
with the same name and even possibly, their initials. So, it
For the record, I didn't create the solution. I'm only correcting the
mistakes that someone else left behind. The new account feature I just
implemented does exactly what you described below ...
CSR will likely be manually correcting this as they get user's complaints
with login problems. They
Dusty,
I was not inferring that you had programmed a process that had created the
problem in the first place.
It really doesn't matter who created the problem other than the fact you are
the one handling it and making sure that the process is more efficient.
I also describe things from a
No worries Teddy. I just didn't want you to get the idea that I might be so
careless as to create a system that would allow new account users to choose
a duplicate username. I would think that any developer with basic skills
would know not to do this and it did seem careless to me that the
No disrespect at all.
It was more of a public statement really. Our goals are to give suggestions
and help people learn from either mistakes we made or heard others make.
We have all done something that may not have been the best solution at the time
until later we realized the impact.
On this very topic...
Duplicate usernames will happen over time, we may as well design for
it. That means the username is not used in any data relationships,
the primary key of the users table is. This allows different dsaxe
users over time which are tied to different data sets in the
16 matches
Mail list logo
