Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
| Package | Version | Downloads · 30d | Trend · 30d |
|---|---|---|---|
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — |
README badges
Embed a badge in your README or website.
Live mentions · last 30 days
Mentions
@RyanJ_KOL This is true and it was exactly my problem last night. See this enumeration for example (github.com/mikependon/RepoDB/blob/master/src/Sche…), I have to it so the target providers know how to evalulate the source default values. Like if SQL Server used the GETUCTDATETIME(), it will be NOW() or CURRENT_TIMESTAMP to PostgreSQL for the column default values. And while the Studio and the underlying libraries are still being developed, we will catch more of this there. Why does it need to be enumeration than interface is a deliberate decision. I am still thinking to refactor this if needed.
@mike_pendon Are you ready? 😅 RepoDB#1374
@awakecoding It is also on our versioning policy at github.com/mikependon/RepoDB/blob/master/VERSIONI…
@mike_pendon Here's a pull request for Turso support in RepoDB: RepoDB#1370
@awakecoding This is a sample implementation from SqLite, which I guess we can easily write for Turso. Link: github.com/mikependon/RepoDB/tree/master/src/Prov… Let me know if you are open. I will handle all Unit, Integration Tests and Documentations.