> -Original Message-
> From: John Meyer [mailto:john.l.me...@gmail.com]
> Sent: Monday, January 18, 2010 5:04 PM
> To: co...@obviouslymalicious.com; mysql@lists.mysql.com
> Subject: Re: Record old passwords ?
>
> Although, on an OT, forcing people to not use a password that they
> have
Nick,
select * from endOfDayData where endOfDayData.market like 'NYMEX'
and endOfDayData.symbol IN (select names.symbol from names where
names.market like 'NYMEX' and names.name like 'natural gas {%');
Query c seems to have good syntax as neither the command line mysql
interface nor the gui s
Thanks! - I found a Insert Into on your tip:
Insert Into Lieferanten (Lieferant)
select distinct
a.lieferant
from artikelstamm a
left join lieferanten b on
a.lieferant = b.lieferant
where
b.lieferant is null
-Ursprüngliche Nachricht-
Von: Carlos Proal [mailto:carlos.pr...@gma
Nick Torenvliet wrote:
Hey all...
I am having a problem with sub-queries that I cannot trouble shoot.
I run query a:
select symbol from names where market like 'NYMEX' and name like 'natural
gas {%';
and get 168 names that I manually insert into query b:
select * from endOfDayData where endO
In the last episode (Jan 19), Nick Torenvliet said:
> Hey all...
>
> I am having a problem with sub-queries that I cannot trouble shoot.
>
> I run query a:
> select symbol from names where market like 'NYMEX' and name like 'natural
> gas {%';
>
> and get 168 names that I manually insert into qu
Hey all...
I am having a problem with sub-queries that I cannot trouble shoot.
I run query a:
select symbol from names where market like 'NYMEX' and name like 'natural
gas {%';
and get 168 names that I manually insert into query b:
select * from endOfDayData where endOfDayData.market like 'NYM
Hi !!
You need a left join and then an insert.
Please read: http://dev.mysql.com/doc/refman/5.1/en/join.html or google
for tutorials on left join
And tell me if you have further questions
Carlos
On 1/19/2010 1:00 PM, Intell! Soft wrote:
Hey
Not really quick ;> - But nobody knows an a
Hey
Not really quick ;> - But nobody knows an answer?
THX
-Ursprüngliche Nachricht-
Von: Intell! Soft [mailto:intellis...@fachoptiker.net]
Bereitgestellt: Donnerstag, 14. Jänner 2010 17:40
Bereitgestellt in: gmane.comp.db.mysql.general
Unterhaltung: Quick help with Insert
Betreff: Q
Another tidbit about this:
Windows-based browsers apparently translate between CP-1252 and UTF-8
automatically. This generally doesn't cause trouble, but it cost me a lot of
sweat and tears to figure out.
I never looked to see what *nix-based browsers do, I ran out of time and
energy.
Regards
On 19/01/2010 09:14, Tompkins Neil wrote:
I think I will go with the four additional column
approach as I proposed (in the current table) - since this need is a PCI
compliancy security requirement.
Do you have a reference for that? Storing past passwords as additional
fields like that is infl
On 19/01/2010 14:44, Tompkins Neil wrote:
Hi All,
Following on from my earlier email - I've the following question now :
I can enforce that the user can't use the same password as the previous four
- when they change their password. However, the user can manipulate this by
changing the passwor
On 1/19/10 2:19 AM, "Ningappa Koneri" wrote:
> 3.It worked even after removing tag from the head tag as well <-- plz
> through some light y it got displayed at the browser ?
this is not a mysql question. but see:
http://www.w3.org/TR/1999/REC-html401-19991224/charset.html#h-5.2.2
the likelih
Yes, I was thinking something along these lines e.g can only change password
once a day ? Also, what do operating systems like Windows etc do in this
respect ?
Cheers
Neil
On Tue, Jan 19, 2010 at 2:53 PM, David Lazo wrote:
> I would say make it more difficult for the user add another field wit
Hi All,
Following on from my earlier email - I've the following question now :
I can enforce that the user can't use the same password as the previous four
- when they change their password. However, the user can manipulate this by
changing the password four times and then resetting back to ther
Hi
Thanks for all the replies. For your information, we are going to store
passwords using SHA256. I think I will go with the four additional column
approach as I proposed (in the current table) - since this need is a PCI
compliancy security requirement. I can then pull all the data with one
q
15 matches
Mail list logo