![sqleditor filemaker sqleditor filemaker](https://www.getintopces.com/wp-content/uploads/2020/02/razorsql-screenshot-01-1536x847.png)
Come back here and report to me all the brands of English Muffins, and the number in each pack, and whether they are whole wheat or regular wheat or whatever, and how many of each type of package, and the price of". "You there! I want you go into that there grocery store and go to aisle 2 and see if they have English Muffins. If FileMaker were by analogy the experience of actually GOING to the grocery store and being IN the grocery store and going up and down the aisles and seeing what is on the shelves and perhaps editing that by removing a loaf of bread here and a bottle of seltzer there, SQL is a very odd grocery store. Let me tell you what SQL is like instead. There is never at any time an answer to any form of the question "where am I". You cannot be in Browse Mode and just viewing data and when you see a bit you'd like to change you click into the relevant field and type in new information. You do not at any time get to be IN the database doing stuff. And your cursor may be in a field in which case you are IN a field (and this may be true of Find Mode as well). You may also be IN a found set that includes other records as well. Unless you are in Find Mode or Preview Mode, you are also, as a consquence of which record is the active record, ON a specific record. As a consequence of the native table of the table occurrence OF that layout, you are IN a table. You are IN a window, which is the active window. In FileMaker, you yourself always have a context. This, I find, is the biggest conceptual difference between FileMaker and SQL.
![sqleditor filemaker sqleditor filemaker](https://www.fmpromigrator.com/images/fmpro_migrator/Image_Export_SQL_graphics/Image_Export_SQL_Screenshot_546_530.gif)
I can tell you that looking back at that I do not find much to disagree with, but I would stress slightly different things. Preconceptions: I wrote this before diving into MySQL. It was my intent, of course, to use it as a data source for FileMaker 9's (then 10's) ability to use ODBC data sources directly in the same fashion as native FmPro tables, but also to move beyond my elementary ability to muddle my way through a SELECT query and get a better sense of how SQL systems really 'think'.
![sqleditor filemaker sqleditor filemaker](https://www.malcolmhardie.com/support/sqleditor/filemaker/jdbc-panel.png)
The specific environment I have installed and am cutting my SQL teeth on is MySQL. Those of you who are FileMaker-centric as I am, and have yet to mess with SQL to any real extent, may benefit somewhat, and those of you who came IN here to learn FileMaker after already knowing SQL environments may find it amusing and informative to see what your old familiar world looks like from the alien perspective of a FileMaker-centric developer. Having muddled through it a bit this winter and spring, I thought I'd share my perceptions. I never did find any that were truly aimed at the proficient FileMaker developer.
#Sqleditor filemaker mac#
Kind of like a Windows switcher's guide to the Mac or vice versa, I guess the web — Amazon and otherwise — have plenty of guides to SQL, beginner's orientations, SQL for Dummies, etc etc, but some of it assumes you've never met a database before in your life, while some assumes a passing familiarity with relational db theory.