burnstony#1975 Comments - Convex Community

burnstony#1975

Posts Comments

CCConvex Community

•Created by burnstony#1975 on 3/27/2025 in #support-community

Wait for a result

so would an action be useable for a query that you want to not be reactive

6 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

Thank you

54 replies

CCConvex Community

•Created by burnstony#1975 on 3/10/2025 in #support-community

aggregate index

Just found it myself, but you beat me to it, thank you so much I was just going to past the answer back in here

  const startInclusive = request.startInclusive ?? false;

  const startInclusive = request.startInclusive ?? false;

6 replies

CCConvex Community

•Created by burnstony#1975 on 3/10/2025 in #support-community

aggregate index

@lee if so, how do you get the first record?

6 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@lee if I move it fromone file to a different file is it a different aggregate

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@lee I'm confused where the aggregate is, where is the data stored? If I rename it, how do I no the old one is gone?

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

thanks

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@lee thank you (there are no anchor tag links to the sections on this page - which would be nice when sharing them) https://www.convex.dev/components/aggregate Repair incorrect aggregates If some mutation or direct write in the Dashboard updated the source of truth data without writing to the aggregate, they can get out of sync and the returned aggregates may be incorrect. The simplest way to fix is to start over. Either call await aggregate.clear(ctx) or rename the component like app.use(aggregate, { name: "newName" }) which will reset it to be empty. Then follow the instructions from above. There is an alternative which doesn't clear the aggregates: compare the source of truth to the aggregate table. You can use db.query("mytable").paginate() on your Convex table and aggregate.paginate() on the aggregate. Update the aggregates based on the diff of these two paginated data streams.

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@lee I've accidentally inserted everything in the aggregate twice, how do I clear everything from the aggregate or otherwise fix it

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

both seem to work the same, and be reactive, which is pretty cool wondering how ctx.db.query getPage streamQuery are related

export const pageOfTimeline = query({
    args: {
        page: v.number(),
        pageSize: v.number()
    },
    handler: async (ctx, { page, pageSize }) => {
        const count = await timeline_aggregate.count(ctx);
        console.log("count", count);
        const { key } = await timeline_aggregate.at(ctx, (page-1) * pageSize);
        console.log(key);
        let pageData  = getPage(ctx, {
            table: "timeline",
            index: "start_index",
            startIndexKey: key,
            targetMaxRows: pageSize,
            schema: schema  
        });
        return (await pageData).page;
    },
});

export const streamPageOfTimeline = query({
    args: {
        page: v.number(),
        pageSize: v.number()
    },
    handler: async (ctx, { page, pageSize }) => {
      console.log("processLargeDataset")
      const { key } = await timeline_aggregate.at(ctx, (page-1) * pageSize);
      let count = 0;
      const stream = await streamQuery(ctx, {
        table: "timeline",
        index: "start_index",
        order: "asc",
        startIndexKey: key,
        schema: schema, // Your schema definition
      }
      )
      const response: Array<Doc<"timeline">> = []
      console.log("key", key)
      for await (const [doc] of stream) {
        if (count > pageSize) break;
        count++;
        response.push(doc)
      }
      return response;
    },
  });

export const pageOfTimeline = query({
    args: {
        page: v.number(),
        pageSize: v.number()
    },
    handler: async (ctx, { page, pageSize }) => {
        const count = await timeline_aggregate.count(ctx);
        console.log("count", count);
        const { key } = await timeline_aggregate.at(ctx, (page-1) * pageSize);
        console.log(key);
        let pageData  = getPage(ctx, {
            table: "timeline",
            index: "start_index",
            startIndexKey: key,
            targetMaxRows: pageSize,
            schema: schema  
        });
        return (await pageData).page;
    },
});

export const streamPageOfTimeline = query({
    args: {
        page: v.number(),
        pageSize: v.number()
    },
    handler: async (ctx, { page, pageSize }) => {
      console.log("processLargeDataset")
      const { key } = await timeline_aggregate.at(ctx, (page-1) * pageSize);
      let count = 0;
      const stream = await streamQuery(ctx, {
        table: "timeline",
        index: "start_index",
        order: "asc",
        startIndexKey: key,
        schema: schema, // Your schema definition
      }
      )
      const response: Array<Doc<"timeline">> = []
      console.log("key", key)
      for await (const [doc] of stream) {
        if (count > pageSize) break;
        count++;
        response.push(doc)
      }
      return response;
    },
  });

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

Thank you lee, this looks like it should work, basically allowing a take starting at a given index the equivalent of .gt(key).take(n) the AI basically thinks you can do that directly using withindex it also thinks skip is supported

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

but I dont have the aggregate populated yet

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

this runs and seems correct

export const processLargeDataset = query({
  handler: async (ctx) => {
    console.log("processLargeDataset")
    const { key } = await timeline_aggregate.at(ctx, 10);
    let count = 0;
    const stream = await streamQuery(ctx, {
      table: "timeline",
      index: "start_index",
      order: "asc",
      startIndexKey: key,
      schema: schema, // Your schema definition
    }
    )
    const response: Array<Doc<"timeline">> = []
    console.log("key", key)
    for await (const [doc] of stream) {
      if (count > 10) break;
      count++;
      response.push(doc)
    }
    return response;
  },
});

export const processLargeDataset = query({
  handler: async (ctx) => {
    console.log("processLargeDataset")
    const { key } = await timeline_aggregate.at(ctx, 10);
    let count = 0;
    const stream = await streamQuery(ctx, {
      table: "timeline",
      index: "start_index",
      order: "asc",
      startIndexKey: key,
      schema: schema, // Your schema definition
    }
    )
    const response: Array<Doc<"timeline">> = []
    console.log("key", key)
    for await (const [doc] of stream) {
      if (count > 10) break;
      count++;
      response.push(doc)
    }
    return response;
  },
});

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@lee I ran this export const processLargeDataset = query({ handler: async (ctx) => { console.log("processLargeDataset") let count = 0; const stream = await streamQuery(ctx, { table: "timeline", index: "start_index", order: "asc", schema: schema, // Your schema definition } ) for await (const [] of stream) { count++; } return count; }, });

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@lee let me find it

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

this does make me understand the issue

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@Jamie the second Claude link doesn't work Properly setting up the aggregate still seems a little tricky and being able to tell that it is up to date seems unclear

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@Jamie will @lee 's idea work

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@Jamie on most platforms I'd probably just dive into the aggregate, but it seems like a lot of mess and maintenance headache that convex so far has helped me

54 replies

CCConvex Community

•Created by burnstony#1975 on 2/25/2025 in #support-community

pagination

@Jamie What is the index actually implemented as? I am confused why it would be difficult to do gt(key) also confused why it would be difficult to do skip(?) startingAtOffset(?)

54 replies