I need to start to learn about this. Would love to be able to make an Ad Hoc Query for a client to be able to ask AI questions about his data. At first it would only be for owners and users that can have access to all the data. Eventually train the AI to have different levels for different users.
Maybe its a product for Rbase to create, an AI Plug-in for USERS of the databases we create as developers. ________________________________ From: [email protected] <[email protected]> on behalf of Peter Ryan <[email protected]> Sent: Tuesday, April 1, 2025 9:56 AM To: RBASE-L <[email protected]> Subject: [RBASE-L] - Re: Grok 3 AI generated R:Base code from a simple prompt: Can you write code for R:Base version 11 database? For fun , wrote and started training a R-GPT for private use with Open AI AIPRM prompt. When asked "to improve" the code I am impressed with the results and the added documentation COMMENTS to add to the snip of code. Training to specify RBase and ignore R or other code options can narrow or refine the results. Dreaming more about RBase:AI solutions someday ... ________________________________ From: [email protected] on behalf of randyp ctags.com Sent: Tuesday, April 1, 2025 9:25 AM To: RBASE-L Subject: [RBASE-L] - Grok 3 AI generated R:Base code from a simple prompt: Can you write code for R:Base version 11 database? Grok 3. Can you write code for R:Base version 11 database? Yes, I can help you write code for R:BASE Version 11, a relational database management system (RDBMS) that uses its own command syntax for managing and querying databases. R:BASE has a unique programming environment with commands like CREATE, INSERT, SELECT, and RUN, often executed via its command-line interface or stored in script files (e.g., .RMD files). Below, I’ll provide an example of R:BASE code tailored to a simple use case, followed by explanations. Since you haven’t specified a particular task, I’ll assume you’d like a basic example—such as creating a table for tracking Holy week events (tying into your earlier question), inserting data, and querying it. If you have a specific requirement, feel free to clarify! Example R:BASE Code This code creates a table for Holy Week events, inserts data based on John P. Pratt’s 33 AD timeline, and retrieves it. [A previous question I asked, but did not specify for Grok's example. What are the dates and days of events during Holy Week according to John Pratt? ] rbase /* Clear the screen and set up environment */ CLS SET ECHO ON /* Create a database if it doesn’t exist */ CREATE DATABASE HolyWeekDB /* Connect to the database */ CONNECT HolyWeekDB /* Create a table for Holy Week events */ CREATE TABLE HolyWeekEvents ( EventID INTEGER PRIMARY KEY, EventName VARCHAR(50), EventDate DATE, EventDay VARCHAR(20), Description VARCHAR(255) ) /* Insert data for Holy Week 33 AD per John Pratt */ INSERT INTO HolyWeekEvents VALUES ( 1, 'Triumphal Entry', '03/27/0033', 'Sunday', 'Jesus enters Jerusalem on a donkey, greeted with palms.' ) INSERT INTO HolyWeekEvents VALUES ( 2, 'Cleansing of Temple', '03/28/0033', 'Monday', 'Jesus overturns tables in the Temple.' ) INSERT INTO HolyWeekEvents VALUES ( 3, 'Last Supper', '03/31/0033', 'Thursday', 'Jesus shares Passover meal and institutes Eucharist.' ) INSERT INTO HolyWeekEvents VALUES ( 4, 'Crucifixion', '04/01/0033', 'Friday', 'Jesus is crucified and dies at 3 PM.' ) INSERT INTO HolyWeekEvents VALUES ( 5, 'Resurrection', '04/03/0033', 'Sunday', 'Jesus rises from the dead early morning.' ) /* Query the table to display all events */ SELECT EventName, EventDate, EventDay, Description FROM HolyWeekEvents ORDER BY EventDate /* Save the output to a file */ OUTPUT HolyWeekReport.txt LIST ALL OUTPUT SCREEN /* Disconnect and clean up */ DISCONNECT SET ECHO OFF [NOTE: I would put this in the R:Base Editor and check it. But it seems quite complete for a simple request, and 3 minute wait. Lists need a "+" after each comma." Explanation of the Code 1. Environment Setup: * CLS: Clears the screen for a clean display. * SET ECHO ON: Shows commands as they execute (useful for debugging). 2. Database Management: * CREATE DATABASE HolyWeekDB: Creates a new database. If it already exists, you’d use CONNECT directly. * CONNECT HolyWeekDB: Opens the database for operations. 3. Table Creation: * CREATE TABLE HolyWeekEvents: Defines a table with columns: * EventID (INTEGER PRIMARY KEY): Unique identifier. * EventName (VARCHAR(50)): Name of the event. * EventDate (DATE): Date in MM/DD/YYYY format. * EventDay (VARCHAR(20)): Day of the week. * Description (VARCHAR(255)): Brief description. 4. Data Insertion: * INSERT INTO HolyWeekEvents VALUES: Adds rows with Pratt’s 33 AD dates. Note that R:BASE expects dates as strings in MM/DD/YYYY format (e.g., '03/27/0033'). 5. Querying: * SELECT ... FROM HolyWeekEvents: Retrieves and sorts events by date. R:BASE’s SQL-like syntax is straightforward here. 6. Output: * OUTPUT HolyWeekReport.txt: Redirects query results to a text file. * LIST ALL: Displays all table contents (an alternative to SELECT *). * OUTPUT SCREEN: Returns output to the screen. 7. Cleanup: * DISCONNECT: Closes the database connection. * SET ECHO OFF: Stops echoing commands. Running the Code * Interactive Mode: Type this into the R:BASE 11 command prompt line by line. * Script File: Save it as HolyWeek.rbd (or similar), then run it with: RUN HolyWeek.rbd from the R:BASE prompt. Notes for R:BASE 11 * Version Compatibility: This syntax aligns with R:BASE 11’s capabilities (released circa 2019), which supports enhanced SQL features and GUI tools, but the example uses classic command-line style for simplicity. * Date Handling: R:BASE stores dates internally but accepts them as MM/DD/YYYY strings in commands. * Error Handling: Add IF ERROR THEN ... blocks for robustness in production code (e.g., IF ERROR THEN PRINT 'Table creation failed'). If you need a more complex example—like joins, stored procedures (DEFINE PROCEDURE), or integration with forms—let me know what you’re aiming for! -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/rbase-l/PH0PR11MB51122C660E0BC53E2A38C129C7AC2%40PH0PR11MB5112.namprd11.prod.outlook.com<https://groups.google.com/d/msgid/rbase-l/PH0PR11MB51122C660E0BC53E2A38C129C7AC2%40PH0PR11MB5112.namprd11.prod.outlook.com?utm_medium=email&utm_source=footer>. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/rbase-l/SJ2PR17MB713831CEEAC8DB603B29C057C9AC2%40SJ2PR17MB7138.namprd17.prod.outlook.com<https://groups.google.com/d/msgid/rbase-l/SJ2PR17MB713831CEEAC8DB603B29C057C9AC2%40SJ2PR17MB7138.namprd17.prod.outlook.com?utm_medium=email&utm_source=footer>. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/rbase-l/SA1PR19MB51820FB5232D1143401D4C45A8AC2%40SA1PR19MB5182.namprd19.prod.outlook.com.
