Do you think SQL can replace C and java
- Thread starter steelcat
- Start date
Only if ARM DDR3's GPU cores instruction set a new hard drive.
strollin
Well-Known Member
A programming language can't replace SQL and SQL can't replace a programming language.
When you access a database from a program written in C or Java, you generally pass the SQL commands thru the interface as a text string so even if you use a programming language to access a database, you still need to use SQL.
When you access a database from a program written in C or Java, you generally pass the SQL commands thru the interface as a text string so even if you use a programming language to access a database, you still need to use SQL.
TrainTrackHack
VIP Member
SQL was created specifically for database queries, even though it's technically Turing complete it doesn't have the features a more general programming language needs. Hence no-one has and no-one in their right mind would develop interfaces for SQL to access operating system APIs and other libraries (for user interfaces and so on), and before this happens SQL has no hope replacing a real programming language.
In short, no.
In short, no.
Geoff
VIP Member
TrainTrackHack
VIP Member
Of course it is. But SQL was made for database queries, that's why it's called "Structured Query Language". It was designed for a specific domain and it and anything like it would be extremely unwieldy as a general-purpose "real" programming language.
Hammers have few specific uses, and cutting steak isn't one of them. Still nobody disputes that it's possible to cut steak with a hammer; sure, you can do it, but it'll be a pain. Someone might even make a special steak-cutting hammer, but people will still keep using knives and you'll have a hard time convincing them to change.
This is the best analogy I've ever heard...period :good:
In 40 years, SQL has never moved beyond database applications. There is a reason for that
We have languages that are better suited for other tasks. Could you imagine....SELECT wicked_awesome_grapphics INTO video_buffer; SELECT animate_wicked_awesome_graphics INTO gpu;
You'll give people COBOL flashbacks
And those forms that are generated in a database, they aren't written in SQL