db_name stringclasses 146
values | prompt stringlengths 310 4.81k |
|---|---|
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
restaurants | ### Complete SQL query only and with no explanation
### SQL tables followed by foreign key information:
#
# GEOGRAPHIC ( CITY_NAME, COUNTY, REGION )
# RESTAURANT ( ID, NAME, FOOD_TYPE, CITY_NAME, RATING )
# LOCATION ( RESTAURANT_ID, HOUSE_NUMBER, STREET_NAME, CITY_NAME )
#
# RESTAURANT.CITY_NAME can be joined with GEO... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.