Skip to content

Moving D1 shim inside workerd#764

Merged
geelen merged 11 commits intomainfrom
d1-shim-in-workerd
Jun 19, 2023
Merged

Moving D1 shim inside workerd#764
geelen merged 11 commits intomainfrom
d1-shim-in-workerd

Conversation

@geelen
Copy link
Contributor

@geelen geelen commented Jun 13, 2023

Currently trying out using the wrapped binding type to do this without any C++ changes, but difficult to do an e2e test...

@geelen geelen force-pushed the d1-shim-in-workerd branch from 4cb30b4 to 6b0a399 Compare June 14, 2023 02:04
@geelen geelen marked this pull request as ready for review June 14, 2023 23:19
@geelen geelen force-pushed the d1-shim-in-workerd branch 3 times, most recently from 44696ba to 10dfc33 Compare June 15, 2023 06:08
@geelen geelen force-pushed the d1-shim-in-workerd branch from 10dfc33 to ce74b4f Compare June 16, 2023 01:42
@geelen geelen force-pushed the d1-shim-in-workerd branch from ebb770c to d5e77b3 Compare June 19, 2023 22:21
first<T = unknown>(): Promise<Record<string, T> | null>;
run<T = unknown>(): Promise<D1Result<T>>;
all<T = unknown>(): Promise<D1Result<T>>;
all<T = unknown>(): Promise<D1Result<T[]>>;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is causing issues. D1Result has the property results: T[]; putting T as an array. This change is saying all() returns an array of arrays as the result. This needs to be reverted, or D1Result needs to be updated to results: T; if run() doesn't return an array in results. But I think it is the former.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants