Val Town Code SearchReturn to Val Town

API Access

You can access search results via JSON API by adding format=json to your query:

https://codesearch.val.run/$%7BsvgDataUrl%7D?q=database&page=17&format=json

For typeahead suggestions, use the /typeahead endpoint:

https://codesearch.val.run/typeahead?q=database

Returns an array of strings in format "username" or "username/projectName"

Found 7799 results for "database"(1632ms)

ai-promptedknowledge.md2 matches

@cricks_unmixed4uโ€ขUpdated 4 days ago
219```
220โ”œโ”€โ”€ backend/
221โ”‚ โ”œโ”€โ”€ database/
222โ”‚ โ”‚ โ”œโ”€โ”€ migrations.ts # Schema definitions
223โ”‚ โ”‚ โ”œโ”€โ”€ queries.ts # DB query functions
278 ```
279
280### Database Patterns
281- Run migrations on startup or comment out for performance
282- Change table names when modifying schemas rather than altering

thirdTimervaltown.mdc2 matches

@charmaineโ€ขUpdated 4 days ago
179```
180โ”œโ”€โ”€ backend/
181โ”‚ โ”œโ”€โ”€ database/
182โ”‚ โ”‚ โ”œโ”€โ”€ migrations.ts # Schema definitions
183โ”‚ โ”‚ โ”œโ”€โ”€ queries.ts # DB query functions
239 ```
240
241### Database Patterns
242- Run migrations on startup or comment out for performance
243- Change table names when modifying schemas rather than altering

GlancergetRelatedPagesFromDatabase.ts4 matches

@lightweightโ€ขUpdated 4 days ago
6});
7
8export async function getRelatedPagesFromDatabase(pageId: string) {
9 try {
10 const response = await notion.databases.query({
11 database_id: Deno.env.get("GLANCE_CONTENT_DB_ID"),
12 filter: {
13 property: "Glancer demos", // the property in the Glancer content database that connects to the /demo
14 relation: {
15 contains: pageId, // the Glancer demos property holds the /demo page id to which it is related

Glancerdemo.ts1 match

@lightweightโ€ขUpdated 4 days ago
1import { Hono } from "npm:hono";
2import { getPage } from "../../controllers/getPage.ts";
3import { getDatabase } from "../../controllers/getDatabase.ts";
4
5const app = new Hono();

Glancerapi.ts2 matches

@lightweightโ€ขUpdated 4 days ago
3// Import route modules
4import cobrowse from "./cobrowse.ts";
5import database from "./database.ts";
6import demo from "./demo.ts";
7import page from "./page.ts";
12
13// mount routes
14app.route("/db", database);
15app.route("/page", page);
16app.route("/cobrowse", cobrowse);

Glancer_TestsetAction.ts1 match

@charmaineโ€ขUpdated 4 days ago
12 console.log(data);
13 try {
14 // create a database page in the interactions database
15 const page = await setAction(data);
16 // console.log(page);

Glancer_TestsetAction.ts1 match

@charmaineโ€ขUpdated 4 days ago
10 const page = await notion.pages.create({
11 parent: {
12 database_id: Deno.env.get("GLANCE_INTERACTIONS_DB_ID"),
13 },
14 properties: {

Glancer_TestservePDF.ts1 match

@charmaineโ€ขUpdated 4 days ago
8
9 // get each of the actions from this demo from Notion
10 // data is stored in the "Glancer interactions" database and attached to the demo via relation
11 // we can't really use the relation property b/c that only holds an array of page IDs in Notion
12 // so, in Notion, we use a formula to transform the relation array into a string

Glancer_TestREADME.md10 matches

@charmaineโ€ขUpdated 4 days ago
221```typescript
222export default async function (interval: Interval) {
223 const pages = await notion.databases.query({
224 database_id: Deno.env.get("GLANCE_DEMOS_DB_ID"),
225 });
226
244});
245
246const databaseId = Deno.env.get("GLANCE_DEMOS_DB_ID");
247```
248
250
251- `NOTION_API_KEY`: Notion integration token
252- `GLANCE_DEMOS_DB_ID`: Notion database ID for demo pages
253- `GLANCE_INTERACTIONS_DB_ID`: Notion database ID for interaction tracking
254
255## Project Conventions
291- `/api/*`: JSON data endpoints for frontend consumption
292- `/demo/*`: Personalized demo page serving with data injection
293- `/tasks/*`: Notion webhook processing and database updates
294
295## External Dependencies
300
301- **Email and Alerting**: Slack notifications and email alerts are configured within Notion
302- **Database Management**: Three core Notion databases power the application:
303 - **Glancer Demos Database**: Stores demo configurations, visitor information, and personalization data
304 - **Glancer Interactions Database**: Warehouses demo events, clicks, and user behavior analytics
305 - **Glancer Agents Database**: Manages agent assignments, availability, and contact information
306
307The Val Town application serves as an automation and presentation layer that extends Notion's native capabilities, providing real-time cobrowsing experiences while maintaining all data persistence and workflow management within the Notion ecosystem.

Glancer_TestINSTRUCTIONS.md5 matches

@charmaineโ€ขUpdated 4 days ago
43- blob storage for the cache, which enables snappy demos
44- cron(s) that keep the cache up-to-date
45- environment variables, which we use to store connection details for Notion, database ids for essential Notion databases (including the demos and interactions databases)
46- logging features
47
63
64- email and other alerting (e.g., Slack)
65- databases, including:
66 - the "Glancer demos" database
67 - the "Glancer interactions" database, which is where certain demo events (e.g., clicks) are warehoused and visualized
68 - the "Glancer agents" database, which handles agent assignments and management
69
70Note that this app integrates with Notion to extend Notion in important ways; namely, automation and logging. Please be clear about that.

bookmarksDatabase

@s3thiโ€ขUpdated 4 months ago

sqLiteDatabase1 file match

@ideofunkโ€ขUpdated 7 months ago