Re: Meaning of 1:1, 1:1 generalization, 1:n, 1:n non identifying, n:m

2004-10-02 Thread GH
weird... about 1:! generalization and 1:m non identifying... 

I think that these examples can make it better to understand some of
those terms... I am quoting from Database Systems -- Design,
Implementation  Management fouth edition by Rob  Coronel (page 23)

Conceptual Modules use three types of relationships to descrive
associates amond data: one-to-many, many-to-many, and one-to-one.
Database designers usually use shorthand notations 1:M, M:N, and 1:1
for them, respectfully. The following examples illustrate the
distinctions among the three.

1. *ONE-TO-MANY Relationships* A painter pains many diffrent
paintings, but each one of hem is painted by only that painter. Thus
the painter (the one) is related to the paintings (the many).
Therefore, database designers lable the relationship PAINTER paints
PAINTINGS as 1:M. Simillarly, a customer account (the one) might
contain many invoices, but those invoices (the many) are related to
only a singe customer account. The CUSTOMER generates INVOICE
relationship would also be labled 1:M

2 *MANY-TO-MANY Relationship* An employee might learn many job skills,
ans each job skill might be learned by many employees. Database
designers label the relationship EMPLOYEE learns SKILL as M:N.
Similarly, a student can take many courses, and each course can be
taken by many students, thus yielding the M:N relationship label for
the relationship for the relationship expressed by STUDENT takes
COURSE

3 *ONE-TO-ONE Relationship* A retail company's management structure
may require that eaco one of its stores be managed by a single
employee. In turn, each store manager -- who is an employee -- only
manages a single store. Therefore the relationship EMPLOYEE manages
STORE is labled 1:1





Hope that this helps... as per the  non identifying and the
generalizations... DUNNO




On Thu, 30 Sep 2004 13:14:03 -0400, Joshua Beall [EMAIL PROTECTED] wrote:
 Hi All,
 
 I've been taking a look at DB Designer 4, and looking through the
 documentation (http://www.fabforce.net/dbdesigner4/doc/index.html) I am a
 little unclear on some of their nomenclature:
 
 '1:1' - Ok, one to one.  Got it.
 '1:1' generalization - Don't know this.  Obviously different somehow from
 one to one, but how?
 '1:n' - One to many, I assume.
 '1:n non identifying' - Nonidentifying?  What does this mean?
 'n:m' - Many to many?  Again, not sure.
 
 Can anyone help clarify?
 
 Thanks!
  -Josh
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Telephone number column not working

2004-10-02 Thread Stuart Felenstein
I have a field telephone.
Set to type :int: 
Length: 11
It's  not working correctly, and not sure if it's my
application or something I have wrongly set up for the
database. 
We are talking about U.S. Telephone numbers here, so 7
digits (area code, exchange, unique number)

Now it seems everything works up to the storing of 6
numbers.  Once I add the 7th number, everything goes
haywire.  The number gets transformed to some totally
different number and / or 0 (zero).

Now I had set up a validation , which I think would be
correct for a U.S. number:

[0-9\+\-\/ \(\)\.]+

Yet, even if I remove that regexp and let it validate
solely on integers: -{0,1}\d+

Nothing.
I thought perhaps enforcing the field to unsigned
might help, but no change.

One last note, I've now added some javascript to
enforce format.  This hasn't changed anything , better
or worse.  Same behaviour.  This is solely for making
sure client enters 111-111- format.  Just wanted
to include this in my information.

Well if anyone has a clue appreicate the help.

Stuart


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread GH
One issue could be that an int column unsigned can only hold up to
4294967295 a ten digit number. Plus if you put it in a context of a
phone number... only area codes 428 or lower will have ALL THE
EXCHANGES and ALL THE UNIQUE NUMBERS in the range... with part of area
code 429

A bigint will hold the complete range you are looking for However,
I would sugest that since you mostlikely are not going to be doing
mathematical operations on a phone number that you use a varchar or
char field.

Maybe someone could correct me but aren't regex for strings only?


Gary




On Sat, 2 Oct 2004 04:59:45 -0700 (PDT), Stuart Felenstein
[EMAIL PROTECTED] wrote:
 I have a field telephone.
 Set to type :int:
 Length: 11
 It's  not working correctly, and not sure if it's my
 application or something I have wrongly set up for the
 database.
 We are talking about U.S. Telephone numbers here, so 7
 digits (area code, exchange, unique number)
 
 Now it seems everything works up to the storing of 6
 numbers.  Once I add the 7th number, everything goes
 haywire.  The number gets transformed to some totally
 different number and / or 0 (zero).
 
 Now I had set up a validation , which I think would be
 correct for a U.S. number:
 
 [0-9\+\-\/ \(\)\.]+
 
 Yet, even if I remove that regexp and let it validate
 solely on integers: -{0,1}\d+
 
 Nothing.
 I thought perhaps enforcing the field to unsigned
 might help, but no change.
 
 One last note, I've now added some javascript to
 enforce format.  This hasn't changed anything , better
 or worse.  Same behaviour.  This is solely for making
 sure client enters 111-111- format.  Just wanted
 to include this in my information.
 
 Well if anyone has a clue appreicate the help.
 
 Stuart
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread Stuart Felenstein
I guess that is why if I enter 703111
I get this back - 4294967295

Stuart


--- GH [EMAIL PROTECTED] wrote:

 One issue could be that an int column unsigned can
 only hold up to
 4294967295 a ten digit number. Plus if you put it in
 a context of a
 phone number... only area codes 428 or lower will
 have ALL THE
 EXCHANGES and ALL THE UNIQUE NUMBERS in the range...
 with part of area
 code 429
 
 A bigint will hold the complete range you are
 looking for However,
 I would sugest that since you mostlikely are not
 going to be doing
 mathematical operations on a phone number that you
 use a varchar or
 char field.
 
 Maybe someone could correct me but aren't regex for
 strings only?
 
 
 Gary
 
 
 
 
 On Sat, 2 Oct 2004 04:59:45 -0700 (PDT), Stuart
 Felenstein
 [EMAIL PROTECTED] wrote:
  I have a field telephone.
  Set to type :int:
  Length: 11
  It's  not working correctly, and not sure if it's
 my
  application or something I have wrongly set up for
 the
  database.
  We are talking about U.S. Telephone numbers here,
 so 7
  digits (area code, exchange, unique number)
  
  Now it seems everything works up to the storing of
 6
  numbers.  Once I add the 7th number, everything
 goes
  haywire.  The number gets transformed to some
 totally
  different number and / or 0 (zero).
  
  Now I had set up a validation , which I think
 would be
  correct for a U.S. number:
  
  [0-9\+\-\/ \(\)\.]+
  
  Yet, even if I remove that regexp and let it
 validate
  solely on integers: -{0,1}\d+
  
  Nothing.
  I thought perhaps enforcing the field to unsigned
  might help, but no change.
  
  One last note, I've now added some javascript to
  enforce format.  This hasn't changed anything ,
 better
  or worse.  Same behaviour.  This is solely for
 making
  sure client enters 111-111- format.  Just
 wanted
  to include this in my information.
  
  Well if anyone has a clue appreicate the help.
  
  Stuart
  
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:   

http://lists.mysql.com/[EMAIL PROTECTED]
  
 
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread Paul DuBois
At 4:59 -0700 10/2/04, Stuart Felenstein wrote:
I have a field telephone.
Set to type :int:
Length: 11
It's  not working correctly, and not sure if it's my
application or something I have wrongly set up for the
database.
We are talking about U.S. Telephone numbers here, so 7
digits (area code, exchange, unique number)
Are you trying to store telephone number values with
the intermediate dashes? Such values are not actually
numbers. You'll need to store them as strings, or
else remove the dashes.
Now it seems everything works up to the storing of 6
numbers.  Once I add the 7th number, everything goes
haywire.  The number gets transformed to some totally
different number and / or 0 (zero).
Now I had set up a validation , which I think would be
correct for a U.S. number:
[0-9\+\-\/ \(\)\.]+
Yet, even if I remove that regexp and let it validate
solely on integers: -{0,1}\d+
Nothing.
I thought perhaps enforcing the field to unsigned
might help, but no change.
One last note, I've now added some javascript to
enforce format.  This hasn't changed anything , better
or worse.  Same behaviour.  This is solely for making
sure client enters 111-111- format.  Just wanted
to include this in my information.
Well if anyone has a clue appreicate the help.
Stuart

--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


RE: Telephone number column not working

2004-10-02 Thread Peter Lovatt
Hi

could it be that the - or a space is upsetting things?

111-111- might be calculated to give -

or if the user enters a space it is no longer an integer

unless you need it to be an integer,  telephone numbers are usually stored
as a char type

HTH

Peter



 -Original Message-
 From: Stuart Felenstein [mailto:[EMAIL PROTECTED]
 Sent: 02 October 2004 13:00
 To: [EMAIL PROTECTED]
 Subject: Telephone number column not working


 I have a field telephone.
 Set to type :int:
 Length: 11
 It's  not working correctly, and not sure if it's my
 application or something I have wrongly set up for the
 database.
 We are talking about U.S. Telephone numbers here, so 7
 digits (area code, exchange, unique number)

 Now it seems everything works up to the storing of 6
 numbers.  Once I add the 7th number, everything goes
 haywire.  The number gets transformed to some totally
 different number and / or 0 (zero).

 Now I had set up a validation , which I think would be
 correct for a U.S. number:

 [0-9\+\-\/ \(\)\.]+

 Yet, even if I remove that regexp and let it validate
 solely on integers: -{0,1}\d+

 Nothing.
 I thought perhaps enforcing the field to unsigned
 might help, but no change.

 One last note, I've now added some javascript to
 enforce format.  This hasn't changed anything , better
 or worse.  Same behaviour.  This is solely for making
 sure client enters 111-111- format.  Just wanted
 to include this in my information.

 Well if anyone has a clue appreicate the help.

 Stuart


 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread Stuart Felenstein

--- Paul DuBois [EMAIL PROTECTED] wrote:

 Are you trying to store telephone number values with
 the intermediate dashes? Such values are not
 actually
 numbers. You'll need to store them as strings, or
 else remove the dashes.


Yes, they made all the difference.  
Set the field type to varchar, and the input type to
string.  Correct numbers including hyphens now in
database.

Wondering about one more issue, could changing this to
input string, leave me open to some type of SQL
injection ?

Stuart

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread Martijn Tonies



 I have a field telephone.
 Set to type :int:
 Length: 11

You cannot store a phone-number in an int.

Use (var)char.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL  MS SQL
Server.
Upscene Productions
http://www.upscene.com



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread Patrick Sherrill
Given the many 'standards' for formatting phone numbers, I would recommend 
using a char or varchar.  Regex is intended for string types.
Do yourself a favor run an alter table and change the column to a char or 
varchar.

I hope this helps...
Pat...
[EMAIL PROTECTED]
CocoNet Corporation
SW Florida's First ISP
- Original Message - 
From: GH [EMAIL PROTECTED]
To: Stuart Felenstein [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, October 02, 2004 8:09 AM
Subject: Re: Telephone number column not working


One issue could be that an int column unsigned can only hold up to
4294967295 a ten digit number. Plus if you put it in a context of a
phone number... only area codes 428 or lower will have ALL THE
EXCHANGES and ALL THE UNIQUE NUMBERS in the range... with part of area
code 429
A bigint will hold the complete range you are looking for However,
I would sugest that since you mostlikely are not going to be doing
mathematical operations on a phone number that you use a varchar or
char field.
Maybe someone could correct me but aren't regex for strings only?
Gary

On Sat, 2 Oct 2004 04:59:45 -0700 (PDT), Stuart Felenstein
[EMAIL PROTECTED] wrote:
I have a field telephone.
Set to type :int:
Length: 11
It's  not working correctly, and not sure if it's my
application or something I have wrongly set up for the
database.
We are talking about U.S. Telephone numbers here, so 7
digits (area code, exchange, unique number)
Now it seems everything works up to the storing of 6
numbers.  Once I add the 7th number, everything goes
haywire.  The number gets transformed to some totally
different number and / or 0 (zero).
Now I had set up a validation , which I think would be
correct for a U.S. number:
[0-9\+\-\/ \(\)\.]+
Yet, even if I remove that regexp and let it validate
solely on integers: -{0,1}\d+
Nothing.
I thought perhaps enforcing the field to unsigned
might help, but no change.
One last note, I've now added some javascript to
enforce format.  This hasn't changed anything , better
or worse.  Same behaviour.  This is solely for making
sure client enters 111-111- format.  Just wanted
to include this in my information.
Well if anyone has a clue appreicate the help.
Stuart
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


data not getting passed to mysql

2004-10-02 Thread tom miller
i'am not sure if this is related to suse 9.1 or what i'am beginning
with mysql and php
i'am running:
mysql 4.0.21-standard
suse9.1
kernel version 2.6.5-7.10b-default
php version 4.3.4 - default install
apache 2.0.49 - prefork

i created an address book using php and when i go thru and fill in
all the required feilds and click on submit it just resets the form.

i was previously using this on mandrake 9.2 and it worked flawlessly
however i was using apache 1.3

i figured it was something worng in my php scripting  but i took a
sample calculator from php.net and it it too was not passing data to
mysql

i have searched google many times over and different forums and never
found my answer or i'am going in the wrong direction. i was looking
into mysql modules that apache uses but that lead to dead ends. looked
into how php handels the data and that too lead me to a dead end. i
wiped my machine out and reinstalled the os figured i missed something
or there was a corrupt file but that apparently was not the case.

if some one could make some helpful suggestions as to whats causing
this i would be much appreciative

thanks

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Looking for null values.

2004-10-02 Thread Scott Hamm
How do I use SQL to look for null values in ANY column?

SELECT * FROM QA WHERE * = null;




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



RE: data not getting passed to mysql

2004-10-02 Thread Donny Simonton
The problem is not a mysql problem, it's a php problem.  It's probably
because you don't have register_globals = On.  The new versions of php have
register_globals off by default.  If you turn it on in the php.ini and
restart apache, I bet it will work.

Then again, I could just blame it on Novell and call it a day.  :)

Donny

 -Original Message-
 From: tom miller [mailto:[EMAIL PROTECTED]
 Sent: Saturday, October 02, 2004 9:43 AM
 To: [EMAIL PROTECTED]
 Subject: data not getting passed to mysql
 
 i'am not sure if this is related to suse 9.1 or what i'am beginning
 with mysql and php
 i'am running:
 mysql 4.0.21-standard
 suse9.1
 kernel version 2.6.5-7.10b-default
 php version 4.3.4 - default install
 apache 2.0.49 - prefork
 
 i created an address book using php and when i go thru and fill in
 all the required feilds and click on submit it just resets the form.
 
 i was previously using this on mandrake 9.2 and it worked flawlessly
 however i was using apache 1.3
 
 i figured it was something worng in my php scripting  but i took a
 sample calculator from php.net and it it too was not passing data to
 mysql
 
 i have searched google many times over and different forums and never
 found my answer or i'am going in the wrong direction. i was looking
 into mysql modules that apache uses but that lead to dead ends. looked
 into how php handels the data and that too lead me to a dead end. i
 wiped my machine out and reinstalled the os figured i missed something
 or there was a corrupt file but that apparently was not the case.
 
 if some one could make some helpful suggestions as to whats causing
 this i would be much appreciative
 
 thanks
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/[EMAIL PROTECTED]
 




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



RE: Looking for null values.

2004-10-02 Thread Donny Simonton
I think you would have to do one column at a time.

Like this.

Select * from QA where title is NULL;

Or you could get a little more crazy with something like this.

Select * from QA where (title is NULL) or (blabla is NULL) or (jimbob is
NULL) or (theskyisfall is NULL);

Donnny

 -Original Message-
 From: Scott Hamm [mailto:[EMAIL PROTECTED]
 Sent: Saturday, October 02, 2004 10:22 AM
 To: [EMAIL PROTECTED]
 Subject: Looking for null values.
 
 How do I use SQL to look for null values in ANY column?
 
 SELECT * FROM QA WHERE * = null;
 
 
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/[EMAIL PROTECTED]
 




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



RE: Looking for null values.

2004-10-02 Thread Scott Hamm
Ok. Will do the crazy mode.  Was thinking maybe there were a shortcut or
something, apparently not.  Thanks though.  Will have to list so many
columns.. *grin*

 -Original Message-
 From: Donny Simonton [SMTP:[EMAIL PROTECTED]
 Sent: Saturday, October 02, 2004 11:31 AM
 To:   'Scott Hamm'; [EMAIL PROTECTED]
 Subject:  RE: Looking for null values.
 
 I think you would have to do one column at a time.
 
 Like this.
 
 Select * from QA where title is NULL;
 
 Or you could get a little more crazy with something like this.
 
 Select * from QA where (title is NULL) or (blabla is NULL) or (jimbob is
 NULL) or (theskyisfall is NULL);
 
 Donnny
 
  -Original Message-
  From: Scott Hamm [mailto:[EMAIL PROTECTED]
  Sent: Saturday, October 02, 2004 10:22 AM
  To: [EMAIL PROTECTED]
  Subject: Looking for null values.
  
  How do I use SQL to look for null values in ANY column?
  
  SELECT * FROM QA WHERE * = null;
  
  
  
  
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:
  http://lists.mysql.com/[EMAIL PROTECTED]
  
 
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Telephone number column not working

2004-10-02 Thread Paul DuBois
At 5:26 -0700 10/2/04, Stuart Felenstein wrote:
--- Paul DuBois [EMAIL PROTECTED] wrote:
 Are you trying to store telephone number values with
 the intermediate dashes? Such values are not
 actually
 numbers. You'll need to store them as strings, or
 else remove the dashes.

Yes, they made all the difference. 
Set the field type to varchar, and the input type to
string.  Correct numbers including hyphens now in
database.

Wondering about one more issue, could changing this to
input string, leave me open to some type of SQL
injection ?
Sure.  That's always true for anything that's a string.
--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Meaning 1:n non identifying

2004-10-02 Thread Donna Hinshaw
A 1:M (one to many) non-identifying means that the associated record in the
-one- table is not a parent of the associated record in the -many- 
table, but
rather just related.

An example:
an identifying 1:M would be a building which has many rooms. The -one- table
carries data about the building .. e.g., street address, number of 
floors, name.
The -many- table carries data about the rooms in the building .. e.g., 
room number,
capacity, special characteristics.  The room cannot exist without the 
building,
therefore this 1:M is an identifying relationship.

a non-identifying 1:M would be a DVD which has many renters. The -one- table
carries data about the DVD... e.g., the movie name, the artist. The 
-many- table
carries data about each person who rents that DVD .. e.g., name, price paid.
The DVD can exist on its own, without ever having been rented, and the 
person
can exist on her own, without ever having rented any DVD, therefore this 1:M
is a non-identifying relationship.

Donna Hinshaw

GH wrote:
weird... about 1:! generalization and 1:m non identifying... 

I think that these examples can make it better to understand some of
those terms... I am quoting from Database Systems -- Design,
Implementation  Management fouth edition by Rob  Coronel (page 23)
Conceptual Modules use three types of relationships to descrive
associates amond data: one-to-many, many-to-many, and one-to-one.
Database designers usually use shorthand notations 1:M, M:N, and 1:1
for them, respectfully. The following examples illustrate the
distinctions among the three.
1. *ONE-TO-MANY Relationships* A painter pains many diffrent
paintings, but each one of hem is painted by only that painter. Thus
the painter (the one) is related to the paintings (the many).
Therefore, database designers lable the relationship PAINTER paints
PAINTINGS as 1:M. Simillarly, a customer account (the one) might
contain many invoices, but those invoices (the many) are related to
only a singe customer account. The CUSTOMER generates INVOICE
relationship would also be labled 1:M
2 *MANY-TO-MANY Relationship* An employee might learn many job skills,
ans each job skill might be learned by many employees. Database
designers label the relationship EMPLOYEE learns SKILL as M:N.
Similarly, a student can take many courses, and each course can be
taken by many students, thus yielding the M:N relationship label for
the relationship for the relationship expressed by STUDENT takes
COURSE
3 *ONE-TO-ONE Relationship* A retail company's management structure
may require that eaco one of its stores be managed by a single
employee. In turn, each store manager -- who is an employee -- only
manages a single store. Therefore the relationship EMPLOYEE manages
STORE is labled 1:1


Hope that this helps... as per the  non identifying and the
generalizations... DUNNO

On Thu, 30 Sep 2004 13:14:03 -0400, Joshua Beall [EMAIL PROTECTED] wrote:
 

Hi All,
I've been taking a look at DB Designer 4, and looking through the
documentation (http://www.fabforce.net/dbdesigner4/doc/index.html) I am a
little unclear on some of their nomenclature:
'1:1' - Ok, one to one.  Got it.
'1:1' generalization - Don't know this.  Obviously different somehow from
one to one, but how?
'1:n' - One to many, I assume.
'1:n non identifying' - Nonidentifying?  What does this mean?
'n:m' - Many to many?  Again, not sure.
Can anyone help clarify?
Thanks!
-Josh
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
   

 



Problem with mysql_fix_privelege_tables

2004-10-02 Thread Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem
I am trying to convert from 3.23 to 4.0

This is what I am getting with or with root:


Script started on Sat Oct  2 16:11:30 2004
doctor.nl2k.ab.ca//usr/contrib/var$ man su
SU(1)BSD Reference Manual
SU(1)

NAME
 su - substitute user identity

SYNOPSIS
 su [-fKlm] [-a auth-type] [-c 
login-class] [login [argument ...]]

DESCRIPTION
 Su requests the Kerberos password for login (or for 
``login.root'', if no login is provided), and switches to that user and 
group ID after obtain-
 ing a Kerberos ticket granting ticket.  A shell is then executed.  Su
 will resort to the local password file to find the password for login if
 there is a Kerberos error, or if the system is not configured for Ker-
 beros.  If su is executed by root, no password is requested and a shell
 with the appropriate user ID is executed; no additional Kerberos tickets
 are obtained.

 By default, the environment is unmodified with the exception of USER,
 LOGNAME, HOME, and SHELL. HOME and SHELL are set to the target login's
 default values.  USER and LOGNAME are set to the target login, unless the
 target login has a user ID of 0 and the -l flag was not specified, in
 which case it is unmodified.  The invoked shell is the target login's.
 This is the traditional behavior of su.
su.0 (27%)
 If not using -m and the target login has a user ID of 0 then the PATH
 variable and umask value (see umask(2))  are always set according to the
 /etc/login.conf file (see login.conf(5)).

 The options are as follows:

 -a  Specify an authentication type.

 -c  Specify a login class.  You may only override the default class
 if you're already root.

 -f  If the invoked shell is csh(1),  this option prevents it from
 reading the ``.cshrc'' file.  (The [f] option may be passed as a
 shell argument after the login name, so this option is redundant
 and obsolescent.)

 -K  Do not attempt to use Kerberos to authenticate the user.

 -l  Simulate a full login.  The environment is discarded except for
 HOME, SHELL, PATH, TERM, LOGNAME, and USER. HOME and SHELL are
 modified as above.  USER and LOGNAME are set to the target login.
 PATH is set to the path specified in the /etc/login.conf file.
 TERM is imported from your current environment.  The invoked
su.0 (52%) shell is the target login's, 
and su will change directory to the
 target login's home directory.

 -m  Leave the environment unmodified.  The invoked shell is your 
lo-
 gin shell, and no directory changes are made.  As a security pre-
 caution, if the target user's shell is a non-standard shell (as
 defined by getusershell(3))  and the caller's real uid is non-ze-
 ro, su will fail.

 The -l and -m options are mutually exclusive; the last one 
specified
 overrides any previous ones.

 Any arguments after the login name are passed to the shell.  This feature
 may be used to execute commands as another user without starting up an
 interactive shell, which may be especially useful in the rc(8) script.

 Only users in group 0 (normally ``wheel'') can su to ``root''.

 By default (unless the prompt is reset by a startup file) the super-user
 prompt is set to ``#'' to remind one of its awesome power.

EXAMPLES
 su daemon /usr/contrib/lib/shell-script arguments
 su news -c 'cd /var/spool/news; du -s * | mail usenet'
su.0 (76%)
SEE ALSO
 csh(1),  kerberos(1),  kinit(1),  setusercontext(3),  group(5),
 login.conf(5),  passwd(5),  environ(7),  login(8),  sh(1)

ENVIRONMENT
 Environment variables used by su:

 HOME  Default home directory of real user ID unless modified as specified
   above.

 LOGNAME
   Same as USER.

 PATH  Default search path of real user ID unless modified as specified
   above.

 TERM  Provides terminal type which may be retained for the substituted
   user ID.

 USER  The user ID is always the effective ID (the target user ID) after
   an su unless the user ID is 0 (root) and the -l flag 
was not speci-   fied.

su.0 (93%)HISTORY
 A 

mysql_fix_privilege_tables again

2004-10-02 Thread Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem
New error WITH password implemented:


Script started on Sat Oct  2 16:28:59 2004
command sent
This scripts updates the mysql.user, mysql.db, mysql.host and the
mysql.func tables to MySQL 3.22.14 and above.

This is needed if you want to use the new GRANT functions,
CREATE AGGREGATE FUNCTION or want to use the more secure passwords in 3.23

If you get 'Access denied' errors, you should run this script again
and give the MySQL root user password as an argument!
Converting all privilege tables to MyISAM format
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'db' is read only
ERROR 1036 at line 3: Table 'host' is read only
ERROR 1036 at line 4: Table 'func' is read only
ERROR 1036 at line 5: Table 'columns_priv' is read only
ERROR 1036 at line 6: Table 'tables_priv' is read only

If your tables are already up to date or partially up to date you will
get some warnings about 'Duplicated column name'. You can safely ignore these!
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'user' is read only

Creating Grant Alter and Index privileges if they don't exists
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'host' is read only
ERROR 1036 at line 3: Table 'db' is read only

Setting default privileges for the new grant, index and alter privileges
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'db' is read only
ERROR 1036 at line 3: Table 'host' is read only

Adding columns needed by GRANT .. REQUIRE (openssl)
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 6: Table 'user' is read only

Creating the new table and column privilege tables
Changing name of columns_priv.Type - columns_priv.Column_priv
You can ignore any Unknown column errors from this
ERROR 1036 at line 1: Table 'columns_priv' is read only

Fixing the func table
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'func' is read only

Adding new fields used by MySQL 4.0.2 to the privilege tables
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'user' is read only

Updating new privileges in MySQL 4.0.2 from old ones
ERROR 1036 at line 1: Table 'user' is read only

ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 1: Table 'db' is read only
ERROR 1036 at line 4: Table 'host' is read only
ERROR 1036 at line 1: Table 'db' is read only
ERROR 1036 at line 2: Table 'host' is read only
ERROR 1036 at line 3: Table 'user' is read only
ERROR 1036 at line 4: Table 'tables_priv' is read only
ERROR 1036 at line 5: Table 'tables_priv' is read only
ERROR 1036 at line 6: Table 'columns_priv' is read only
ERROR 1036 at line 8: Table 'db' is read only
ERROR 1036 at line 9: Table 'host' is read only
ERROR 1036 at line 10: Table 'user' is read only
ERROR 1036 at line 11: Table 'func' is read only
ERROR 1036 at line 12: Table 'tables_priv' is read only
ERROR 1036 at line 13: Table 'columns_priv' is read only
doctor.nl2k.ab.ca//usr/contrib/var$ exit
exit

Script done on Sat Oct  2 16:29:27 2004

Say what??

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: php pages not inserting data into table

2004-10-02 Thread Seth Seeger
Could this be a 'register_globals' issue?  (Check your php.ini file.) 
Are you sure that the queries you're sending are correct?  Is
mysql_query() returning any errors?

Some more information, please!

Seth


On Fri, 1 Oct 2004 23:35:09 -0500, tom miller [EMAIL PROTECTED] wrote:
 i'am not sure if this is related to suse 9.1 or what i'am beginning
 with mysql and php
 i'am running:
 mysql 4.0.21-standard
 suse9.1
 kernel version 2.6.5-7.10b-default
 php version 4.3.4 - default install
 apache 2.0.49 - prefork
 
 i created an address book using php and when i go thru and fill in
 all the required feilds and click on submit it just resets the form.
 
 i was previously using this on mandrake 9.2 and it worked flawlessly
 however i was using apache 1.3
 
 i fifgured it was something worng in my php scripting  but i took a
 sample calculator from php.net and it it too was not passing data to
 mysql
 
 i have searched google many times over and different forums and never
 found my answer or i'am going in the wrong direction. i was looking
 into mysql modules that apache uses but that lead to dead ends. looked
 into how php handels the data and that too lead me to a dead end. i
 wiped my machine out and reinstalled the os figured i missed something
 or there was a corrupt file but that apparently was not the case.
 
 if some one could make some helpful suggestions as to whats causing
 this i would be much appreciative
 
 thanks
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Problem with mysql_fix_privelege_tables

2004-10-02 Thread Paul DuBois
At 16:23 -0600 10/2/04, Dave Shariff Yadallee -  System 
Administrator a.k.a. The Root wrote:
I am trying to convert from 3.23 to 4.0
This is what I am getting with or with root:
Looks like you're confusing the Unix root user with the MySQL root user.
You don't need to use su to run mysql_fix_privilege_tables.


Script started on Sat Oct  2 16:11:30 2004
doctor.nl2k.ab.ca//usr/contrib/var$ man su
SU(1)BSD Reference Manual 
SU(1)


NAME
 su - substitute user identity

SYNOPSIS
 su [-fKlm] [-a 
auth-type] [-c login-class] [login 
[argument ...]]


DESCRIPTION
 Su requests the Kerberos password for login 
(or for ``login.root'', if no login is provided), and 
switches to that user and group ID after obtain-

 ing a Kerberos ticket granting ticket.  A shell is then 
executed.  Su

 will resort to the local password file to find the password for 
login if

 there is a Kerberos error, or if the system is not configured for Ker-
 beros.  If su is executed by root, no password is 
requested and a shell

 with the appropriate user ID is executed; no additional Kerberos tickets
 are obtained.

 By default, the environment is unmodified with the exception of USER,
 LOGNAME, HOME, and SHELL. HOME and SHELL are set to the target login's
 default values.  USER and LOGNAME are set to the target login, unless the
 target login has a user ID of 0 and the -l flag was 
not specified, in

 which case it is unmodified.  The invoked shell is the target login's.
 This is the traditional behavior of su.
su.0 (27%)
 If not using -m and the target login has a user ID 
of 0 then the PATH

 variable and umask value (see umask(2))  are always set according to the
 /etc/login.conf file (see login.conf(5)).

 The options are as follows:

 -a  Specify an authentication type.

 -c  Specify a login class.  You may only 
override the default class

 if you're already root.

 -f  If the invoked shell is csh(1),  this option 
prevents it from

 reading the ``.cshrc'' file.  (The [f] option 
may be passed as a

 shell argument after the login name, so this option is redundant
 and obsolescent.)

 -K  Do not attempt to use Kerberos to 
authenticate the user.


 -l  Simulate a full login.  The environment is 
discarded except for

 HOME, SHELL, PATH, TERM, LOGNAME, and USER. HOME and SHELL are
 modified as above.  USER and LOGNAME are set to the target login.
 PATH is set to the path specified in the 
/etc/login.conf file.

 TERM is imported from your current environment.  The invoked
su.0 (52%) shell is 
the target login's, and su will change directory to the

 target login's home directory.

 -m  Leave the environment unmodified.  The 
invoked shell is your lo-

 gin shell, and no directory changes are made.  As a security pre-
 caution, if the target user's shell is a non-standard shell (as
 defined by getusershell(3))  and the caller's real uid is non-ze-
 ro, su will fail.

 The -l and -m options are mutually 
exclusive; the last one specified

 overrides any previous ones.

 Any arguments after the login name are passed to the shell.  This feature
 may be used to execute commands as another user without starting up an
 interactive shell, which may be especially useful in the rc(8) script.

 Only users in group 0 (normally ``wheel'') can su to ``root''.

 By default (unless the prompt is reset by a startup file) the super-user
 prompt is set to ``#'' to remind one of its awesome power.

EXAMPLES
 su daemon /usr/contrib/lib/shell-script arguments
 su news -c 'cd /var/spool/news; du -s * | mail usenet'
su.0 (76%)
SEE ALSO
 csh(1),  kerberos(1),  kinit(1),  setusercontext(3),  group(5),
 login.conf(5),  passwd(5),  environ(7),  login(8),  sh(1)

ENVIRONMENT
 Environment variables used by su:

 HOME  Default home directory of real user ID unless modified as specified
   above.

 LOGNAME
   Same as USER.

 PATH  Default search path of real user ID unless modified as specified
   above.

 TERM  Provides terminal type which may be retained for the substituted
   user ID.

 USER  The user ID is always the 

Re: mysql_fix_privilege_tables again

2004-10-02 Thread Paul DuBois
At 16:31 -0600 10/2/04, Dave Shariff Yadallee -  System 
Administrator a.k.a. The Root wrote:
New error WITH password implemented:
Apparently the ownership of the mysql database and/or the files in
it is not set such that the files are accessible to the Unix account
that you're using to run mysqld.
For example, perhaps you're running the server as the mysql login user,
but the files are owned by root.  That's a common problem.
Script started on Sat Oct  2 16:28:59 2004
command sent
This scripts updates the mysql.user, mysql.db, mysql.host and the
mysql.func tables to MySQL 3.22.14 and above.
This is needed if you want to use the new GRANT functions,
CREATE AGGREGATE FUNCTION or want to use the more secure passwords in 3.23
If you get 'Access denied' errors, you should run this script again
and give the MySQL root user password as an argument!
Converting all privilege tables to MyISAM format
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'db' is read only
ERROR 1036 at line 3: Table 'host' is read only
ERROR 1036 at line 4: Table 'func' is read only
ERROR 1036 at line 5: Table 'columns_priv' is read only
ERROR 1036 at line 6: Table 'tables_priv' is read only
If your tables are already up to date or partially up to date you will
get some warnings about 'Duplicated column name'. You can safely ignore these!
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'user' is read only
Creating Grant Alter and Index privileges if they don't exists
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'host' is read only
ERROR 1036 at line 3: Table 'db' is read only
Setting default privileges for the new grant, index and alter privileges
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 2: Table 'db' is read only
ERROR 1036 at line 3: Table 'host' is read only
Adding columns needed by GRANT .. REQUIRE (openssl)
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 6: Table 'user' is read only
Creating the new table and column privilege tables
Changing name of columns_priv.Type - columns_priv.Column_priv
You can ignore any Unknown column errors from this
ERROR 1036 at line 1: Table 'columns_priv' is read only
Fixing the func table
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'func' is read only
Adding new fields used by MySQL 4.0.2 to the privilege tables
You can ignore any Duplicate column errors
ERROR 1036 at line 1: Table 'user' is read only
Updating new privileges in MySQL 4.0.2 from old ones
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 1: Table 'user' is read only
ERROR 1036 at line 1: Table 'db' is read only
ERROR 1036 at line 4: Table 'host' is read only
ERROR 1036 at line 1: Table 'db' is read only
ERROR 1036 at line 2: Table 'host' is read only
ERROR 1036 at line 3: Table 'user' is read only
ERROR 1036 at line 4: Table 'tables_priv' is read only
ERROR 1036 at line 5: Table 'tables_priv' is read only
ERROR 1036 at line 6: Table 'columns_priv' is read only
ERROR 1036 at line 8: Table 'db' is read only
ERROR 1036 at line 9: Table 'host' is read only
ERROR 1036 at line 10: Table 'user' is read only
ERROR 1036 at line 11: Table 'func' is read only
ERROR 1036 at line 12: Table 'tables_priv' is read only
ERROR 1036 at line 13: Table 'columns_priv' is read only
doctor.nl2k.ab.ca//usr/contrib/var$ exit
exit
Script done on Sat Oct  2 16:29:27 2004
Say what??
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]