How do I fix this problem with the incorrect syntax

Question

0.00/5 (No votes)

See more:

I keep getting an incorrect syntax near message when I type this code

where it says "Not" on the price double section and "(publisher_id));" on the last section . what should I do??

What I have tried:

SQL

use bookstore
CREATE TABLE book (
book_id int PRIMARY KEY,
isbn VARCHAR(100) NOT NULL,
title VARCHAR(100) NOT NULL,
print_year int NOT NULL,
edition int NOT NULL,
price double NOT NULL,
publisher_id int FOREIGN KEY REFERENCES
publisher(publisher_id)
);

Posted 8-May-22 13:18pm

Jake Aguirre

Updated 8-May-22 17:36pm

Graeme_Grant

v2

Add a Solution

Comments

Mike Hankey 8-May-22 21:08pm

Comma at end of line after REFERENCES i.e. ...REFERENCES,

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

k5054 · Answer 1 · 2022-05-08T15:36:00

Both PostgreSQL and sqlite choke on

SQL

publisher_id FOREIGN KEY REFERENCES publisher(publisher_id)

In both cases removing FOREIGN KEY solved the issue. PostgreSQL did not like the field type of double, as I believe float is the standard type for a floating point field. That being said, a field representing a monetary value is probably better represented as a NUMERIC type, rather than a binary floating point. That's due to the nature of binary floating point, which cannot represent 0.01 exactly. To see this for yourself, try this in your favorite compiled language:

PsueoCode

double d = 0.0;
for 1 ... 100 
   d = d + 0.01

if d == 1.0
    print yes
else
    print no

The result may not be what you expect!