The Interview platform allows you to create custom databases and attach them to questions to assess a candidate’s data processing skills. Click on an item in the table of contents below to learn more about using the database feature.<\/p>\n\n\n\n
\n\u2705 If you’re using a multi-file language you can add a database file directly to the file directory when you create the question<\/a>.<\/p>\n\n\n\nFor example, a Node pad runs a Node.js Express application with a built-in connection to a PostgreSQL database. We’ve also installed Sequelize, a promise-based ORM tool that simplifies interactions with the database. You can find more details in the server.ts<\/code> file. To set up a database in a Node pad, you can either run a database initialization script or do so via an API endpoint, like those in server.ts<\/code>.<\/p>\n<\/blockquote>\n\n\n\nYou can upload custom databases and attach them to questions to test a candidate\u2019s ability to manage, write, and edit database queries either using SQL or a language ORM\/adaptor<\/a>.<\/p>\n\n\n\n\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2705 If you’re using a multi-file language you can add a database file directly to the file directory when you create the question<\/a>.<\/p>\n\n\n\nFor example, a Node pad runs a Node.js Express application with a built-in connection to a PostgreSQL database. We’ve also installed Sequelize, a promise-based ORM tool that simplifies interactions with the database. You can find more details in the server.ts<\/code> file. To set up a database in a Node pad, you can either run a database initialization script or do so via an API endpoint, like those in server.ts<\/code>.<\/p>\n<\/blockquote>\n\n\n\nYou can upload custom databases and attach them to questions to test a candidate\u2019s ability to manage, write, and edit database queries either using SQL or a language ORM\/adaptor<\/a>.<\/p>\n\n\n\n\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
For example, a Node pad runs a Node.js Express application with a built-in connection to a PostgreSQL database. We’ve also installed Sequelize, a promise-based ORM tool that simplifies interactions with the database. You can find more details in the server.ts<\/code> file. To set up a database in a Node pad, you can either run a database initialization script or do so via an API endpoint, like those in server.ts<\/code>.<\/p>\n<\/blockquote>\n\n\n\nYou can upload custom databases and attach them to questions to test a candidate\u2019s ability to manage, write, and edit database queries either using SQL or a language ORM\/adaptor<\/a>.<\/p>\n\n\n\n\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
server.ts<\/code> file. To set up a database in a Node pad, you can either run a database initialization script or do so via an API endpoint, like those in server.ts<\/code>.<\/p>\n<\/blockquote>\n\n\n\nYou can upload custom databases and attach them to questions to test a candidate\u2019s ability to manage, write, and edit database queries either using SQL or a language ORM\/adaptor<\/a>.<\/p>\n\n\n\n\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
server.ts<\/code>.<\/p>\n<\/blockquote>\n\n\n\nYou can upload custom databases and attach them to questions to test a candidate\u2019s ability to manage, write, and edit database queries either using SQL or a language ORM\/adaptor<\/a>.<\/p>\n\n\n\n\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
You can upload custom databases and attach them to questions to test a candidate\u2019s ability to manage, write, and edit database queries either using SQL or a language ORM\/adaptor<\/a>.<\/p>\n\n\n\n\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\n\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\nTo start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2705 Interview’s custom databases are available for MySQL and PostgreSQL.<\/p>\n<\/blockquote>\n\n\n\n
To start, navigate to your Interview dashboard and click Databases <\/strong>in the left-side navigation bar to go to the Custom Databases<\/em> page. Then click Create Database<\/strong>.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAdd a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Add a Title<\/em>, Description<\/em>, and select MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
MySQL<\/code> or PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
PostgreSQL<\/code> from the Language <\/em>dropdown.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nBelow that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n\n<\/a>Interview provides a sample database creation script which includes employees, projects, and department tables. <\/figcaption><\/figure>\n<\/div>\n\n\n\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Below that you’ll see the SQL script that will create the sample database. You can edit this as needed to create your desired database; alternatively you can copy and paste SQL from an existing database into the text box for further customization. <\/p>\n\n\n
\n\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2705 The easiest way to get the raw SQL from an existing database in order to upload it to Interview is with mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
mysqldump<\/code> for MySQL, or pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
pg_dump<\/code> for PostgreSQL. You can upload up to 5 MB of raw SQL.<\/p>\n<\/blockquote>\n\n\n\nVerify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Verify the details and click Save <\/strong>to create the database.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
You\u2019ll see a notification that your database is initializing.<\/p>\n\n\n\n
\n\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\nOnce the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2757If you see an error message, it means your SQL is structured incorrectly. Please correct the errors and try again. <\/p>\n<\/blockquote>\n\n\n\n
Once the database is initialized, you\u2019ll see the Overview <\/strong><\/em>tab which will give you a summary of your custom database. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nYou’ll also see the following tabs.<\/p>\n\n\n\nQuestions<\/strong><\/h3>\n\n\n\nThe Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
You’ll also see the following tabs.<\/p>\n\n\n\n
The Questions<\/em> tab will show you any questions that have the database attached to them. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\nSchema<\/strong><\/h3>\n\n\n\nThe Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Clicking on the question will open it up in the question bank dashboard.<\/p>\n\n\n\n
The Schema <\/em>tab will display the database scheme. You can switch the toggle at the top to switch between the Explorer <\/em>view and the Raw <\/em>view.<\/p>\n\n\n\nThe Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
The Raw <\/em>view displays the standard SQL schema definition:<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
The Explorer<\/em> view displays a graphical representation of the database with tables and relationships between the tables. You can zoom in, zoom out, and click on the screen to move around the schema.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\n\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2705 Both the interviewer and candidate will be able to utilize the Raw <\/em>and Explorer <\/em>views in the pad.<\/p>\n<\/blockquote>\n\n\n\nEdit<\/strong><\/h3>\n\n\n\nThe Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
The Edit <\/em>tab will open the customization page so you can make any changes to the database that need to be made.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\n\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2705 You can reach the Overview<\/em>, Questions, Schema, <\/em>and Edit<\/em> tab options at anytime by navigating to the Custom Database<\/em> page from the left nav menu and then clicking on the View<\/strong> button of the database you want to access.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nIn the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
In the Databases <\/strong>tab on the dashboard you\u2019ll now see your new database in the list of available custom databases.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\n\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u26a0\ufe0f To delete a database, simple click on the three dots to the right of the row and select Delete<\/strong>. Keep in mind that this operation is permanent. <\/p>\n\n\n\n<\/a><\/figure>\n<\/div><\/blockquote>\n\n\n\nAdd a database to a question<\/strong><\/h2>\n\n\n\nCustom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Custom databases must be associated with a question from the Question Bank. You can do this in Step 2 – Add Code Elements<\/em> of question creation or editing by simply selecting your database from the Custom Database <\/em>dropdown menu.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nWhen you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nAccessing the database in the interview<\/strong><\/h2>\n\n\n\nMulti-file languages<\/strong><\/h3>\n\n\n\nYou’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\nExample 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
When you load the question into a pad, the database will be available for querying either directly through MySQL\/PostgresSQL, or through an ORM\/adaptor for languages that have them.<\/p>\n\n\n
You’ll need to use a connector like in one of these Python examples.<\/p>\n\n\n\n
Example 1: <\/strong><\/p>\n\n\nengine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
engine = sqlalchemy.create_engine('postgresql:\/\/coderpad@\/coderpad?host=\/tmp\/postgresql\/socket'<\/span>)<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nExample 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Example 2:<\/strong><\/p>\n\n\ndef<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
def<\/span> read_root<\/span>()<\/span>:<\/span>\n # Replace these with your actual MySQL server information<\/span>\n socket_path = '\/tmp\/mysql\/socket\/mysqld.sock'<\/span>\n user = \"coderpad\"<\/span>\n database_name = \"coderpad\"<\/span>\n\n try<\/span>:\n # Create a connection to the MySQL server using the socket<\/span>\n connection = mysql.connector.connect(\n user=user,\n unix_socket=socket_path,\n database=database_name\n )\n\n if<\/span> connection.is_connected():\n print(\"Connected to MySQL server\"<\/span>)\n\n # Your code for executing SQL queries or operations goes here<\/span>\n cursor = connection.cursor()\n # Execute your SQL queries here<\/span>\n cursor.execute(\"SELECT * FROM employees\"<\/span>)\n\n # Fetch and consume the results<\/span>\n results = cursor.fetchall()\n print(results)\n\n except<\/span> mysql.connector.Error as<\/span> error:\n print(f\"Error: {error}<\/span>\"<\/span>)\n finally<\/span>:\n # Close the connection when done<\/span>\n if<\/span> 'connection'<\/span> in<\/span> locals() and<\/span> connection.is_connected():\n connection.close()\n print(\"Connection closed\"<\/span>)\n return<\/span> {\"Hello\"<\/span>: \"World\"<\/span>}<\/code><\/span>Code language:<\/span> Python<\/span> (<\/span>python<\/span>)<\/span><\/small><\/pre>\n\n\nSingle-file languages<\/strong><\/h3>\n\n\n\nOnce you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\nBoth the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Once you’ve created your question and custom database, the database will automatically be accessible when you create the pad. <\/p>\n\n\n\n
Both the interviewer and candidate will have access to the database schema in the Database<\/em> tab at the top of the right pad pane (1). You can switch between the Raw <\/em>and Explorer<\/em> mode with the toggle button (2). <\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nLike in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Like in the database creation step above, in Explorer <\/em>mode, you can zoom out of the diagram and click and hold the right mouse button to move around the screen:<\/p>\n\n\n\n<\/video><\/figure>\n\n\n\nAs far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n\nVia an ORM or Adaptor<\/a><\/li>\n\n\n\nVia SQL<\/a><\/li>\n<\/ol>\n\n\n\nVia an ORM or Adaptor:<\/strong><\/h4>\n\n\n\nInterview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
As far as accessing the data in the database programmatically, there are two ways to do that within the pad:<\/p>\n\n\n\n
Interview provides common ORM\/adaptor libraries so you can directly query databases from non-database language environments. For example, you can now have candidates load SQL records and interact with them in Python, or show their ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
ActiveRecord<\/code> skills within the Ruby environment.<\/p>\n\n\n\nThis feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n\nJava – JDBC adaptor<\/a><\/li>\n\n\n\nJavascript – Sequelize<\/a>, TypeORM<\/a><\/li>\n\n\n\nPython 2 & 3 – SQLAlchemy<\/a><\/li>\n\n\n\nC++ – MySQL Connector<\/a>, libpqxx (PostgreSQL)<\/a><\/li>\n\n\n\nRuby – ActiveRecord<\/a>, Sequel<\/a><\/li>\n\n\n\nC# – Dapper<\/a>, Entity Framework<\/a>, MySQL Connector<\/a>, Npgsql<\/a><\/li>\n<\/ul>\n\n\n\nTo setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\nOnce you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
This feature is available for the most commonly used languages in Interview, preconfigured with the adaptors listed below. Additional languages may be added based on customer needs.<\/p>\n\n\n\n
To setup data access through an adaptor, you’ll first need to select one of the supported languages listed above from the language dropdown. <\/p>\n\n\n\n
Once you do this, you\u2019ll see a new Database adapters <\/strong>menu appear next to the language; this menu auto-loads the database adaptor.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nClick on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
Click on the dropdown, and choose whether you\u2019d like to use the MySQL <\/strong>or PostgreSQL <\/strong>adaptor. Selecting an adaptor automatically loads example adaptor\/ORM code in the left hand pane (1). You can see your database schema in the right hand pane under the Database<\/strong> tab (2):<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\n\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2757Loading the DB adaptor code will comment out all existing code, including any question code. Best practice is to load the question at the start of the interview, and you may need to rearrange code a little once you load the adaptor. This approach does provide the most flexibility in candidate interview language choice or preferred DB adaptor.<\/p>\n<\/blockquote>\n\n\n\n
\n\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\nKeep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
\u2705 If you do not have a database attached to a question when you select an adaptor package, the pad will load a sample database for you.<\/p>\n<\/blockquote>\n\n\n\n
Keep in mind that the adaptor package is just helper code. As mentioned above<\/a>, you also have the option to paste in the adaptor code when setting up a question. This lets you skip the package loading step, as the database will always be loaded with the question, not the package. <\/strong><\/p>\n\n\n\nThis does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\nVia SQL:<\/strong><\/h4>\n\n\n\nCandidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n\n
This does require you to select a particular language and adaptor for the candidate to use when setting up the question, so there is less flexibility at interview time.<\/p>\n\n\n\n
Candidates can write and run SQL queries against the database at interview in the code editor. Once you select your SQL flavor (MySQL or PostgreSQL), there is no further configuration required.<\/p>\n\n\n