Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Development Tools Database Foundations Manipulating Schema with SQL Altering Tables

Writing SQL Code in an Outdated Version Number: What Happens?

I've been watching quite a few of Andrew's videos on SQL, and he mentions that on the SQL syntax site that there are version numbers for SQL code. I've done some work with XML, which I was using for Android apps, and with that if you use older version numbers the code is wildly different and, in my opinion, harder. There's also a point where the older versions stop being supported. Is all this true of SQL code versions? Like it won't be supported eventually and the code is different from the current version? Also what happens in SQL if you use a really old version of the code now (for some reason you're feeling nostalgic)?

1 Answer

Steven Parker
Steven Parker
230,248 Points

I think most SQL evolution has just been adding new features, I don't think much has ever been deprecated.

A bigger factor to contend with is how database providers tend to do their own custom extensions to SQL, which are not portable. So generally when you encounter syntax issues with previously working code, it's not how old it is but what flavor of database it was developed on (Oracle/MySql/Sql Server/etc.).

Will do, that makes a lot of sense...and I'm glad that there isn't depreciation thus far, because that adds a whole other layer of confusion to things.