-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Jaśkiewicz wrote:
> just outside of your question, you should read about normalization.
> it is in general very bad idea to have a table that holds all
> information possible .
>
I wouldn't say this table is not normalized.
The only fields y
Kusuma Pabba wrote:
when creating tables,
in my sql i have used create table
By "my SQL" I assume you mean MySQL? It took me a minute to figure out
that you didn't mean "in my sql code" but rather "in the product MySQL".
Having read your proposed table definition: I very strongly recommend
On Tue, Feb 17, 2009 at 5:54 AM, Kusuma Pabba wrote:
> while in pgsql i am thinking of to use the same as follows:
>
> CREATE TABLE users (
> user_id int(11) NOT NULL serial,
I see this construct in mysql all the time. Funny thing is most mysql
users think it means an 11 character wide int, i.e
On Tue, Feb 17, 2009 at 04:40:58PM +, Sam Mason wrote:
> > user_name varchar(50) NOT NULL,
>
> As a general design question; should user_name have a UNIQUE
> constraint on it? i.e.
>
> user_name VARCHAR(50) NOT NULL UNIQUE,
Yes, it's good to have a UNIQUE constraint, but not this one
a few further comments:
On Tue, Feb 17, 2009 at 06:54:53PM +0530, Ashish Karalkar wrote:
> CREATE TABLE users (
> user_id serial NOT NULL ,
It's common to combine this with the PRIMARY KEY constraint from below
to be:
user_id SERIAL PRIMARY KEY,
the NOT NULL check is implicit in this and
Kusuma Pabba, 17.02.2009 13:54:
while in pgsql i am thinking of to use the same as follows:
CREATE TABLE users (
user_id int(11) NOT NULL serial,
user_name varchar(50) NOT NULL,
first_name varchar(50) default NULL,
middle_name varchar(50) default NULL,
last_name varchar(50) default NULL,
p
Kusuma Pabba wrote:
when creating tables,
in my sql i have used create table
CREATE TABLE `users` (
`user_id` int(11) NOT NULL auto_increment,
`user_name` varchar(50) NOT NULL,
`first_name` varchar(50) default NULL,
`middle_name` varchar(50) default NULL,
`last_name` varchar(50) default NUL
just outside of your question, you should read about normalization.
it is in general very bad idea to have a table that holds all
information possible .
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/p
when creating tables,
in my sql i have used create table
CREATE TABLE `users` (
`user_id` int(11) NOT NULL auto_increment,
`user_name` varchar(50) NOT NULL,
`first_name` varchar(50) default NULL,
`middle_name` varchar(50) default NULL,
`last_name` varchar(50) default NULL,
`password` varcha
AKHILESH GUPTA schrieb:
> hello everybody
> i am new to this mailing list. this is my first mail to this group.
> i jussst want to confirm that whether is it possible to update a view or
> not??
> i think you all help me in solving my queries in future...!!
Yes it is. All you have
hello everybody
i am new to this mailing list. this is my first mail to this group.
i jussst want to confirm that whether is it possible to update a view or not??
i think you all help me in solving my queries in future...!!
--
Thanks & Regards,
Akhilesh
DAV Institute of Managem
11 matches
Mail list logo
