1,200 karma · joined May 18, 2017
Stripe is buying a lucrative business, but more importantly it is buying the complex knowhow of running an international tax-compliant merchant of record. They can then integrate this into their product. I switched to LemonSqueezy primarily out of concern for EU-wide tax ramifications (EU strikes again). Is there a reason to choose LemonSqueezy over Stripe if you are located in the US? There hasn't been a single VAT-compliance case to my knowledge and the need for MoR is unclear.
It wouldn't surprise me if many VPS use .env files.
The fundamental issue is that you can't control when and how much solar or wind energy to produce and it can't be stored at anywhere the scale needed.
Good ideas are born in your free time when you put the daily work away and are able to zoom out. Returning Monday after a (long) weekend with a pair of new glasses can be profoundly productive.
> The researchers suggest additional work is required to determine the extent to which other farm-associated factors, such as social and maternal interactions, aerial contaminants, antigens from bedding and early nutrition, contributed to the impact of the environment on increased local and systemic immune regulation. [0]
[0]: https://www.sciencedaily.com/releases/2012/02/120208132549.h...
I found that the simpler the better, when testing lots of different SQL schema formats on https://www.sqlai.ai/. CSV (table name, table column, data type) outperformed both a JSON formatted and SQL schema dump. And not to mention consumed fewer tokens.
If you need the database schema in a consistent format (e.g. CSV) just have LLM extract data and convert whatever the user provides into CSV. It shines at this.
I am currently adding public API access to AI-powered text-to-SQL endpoint with RAG support and the my biggest issue is the pricing. Anybody have a ballpark figure what we could be talking about here? Pricing must account for OpenAI tokens (or perhaps letting them add their own OpenAI token), database usage and likely caching/rate limiting setup down the line.
[0]: https://www.sqlai.ai/snippets/cluzdmi8w006d53gt82mguaga
You could ask the same question for any of the nova class 4 products[0].
[0]: https://world.openfoodfacts.org/nova
Edit: This study suggest connection between colon cancer and sugary beverages:
> Conclusion Higher SSB (Sugar-sweetened beverage) intake in adulthood and adolescence was associated with a higher risk of EO-CRC (early-onset colorectal cancer) among women. Reduction of SSB consumption among adolescents and young adults may serve as a potential strategy to alleviate the growing burden of EO-CRC.
For now we don't particularly handle huge schema, being over 10-20k tokens. I would suggest adding only the tables you need. But I will hopefully this week test a solution that automatically pre-determines which tables to include for huge schemas before the actual SQL query generation and thereby using relatively few tokens.
> How easy is it to select which tables should be taken into account?
You can edit the schema using code editor (it will be in CSV). That is relatively easy. I previously had a solution where you could manually tick off tables to include, but found it a bit cumbersome. Might add that back though. Ideally I want everything you run without the user having to include/exclude tables.
> Is there an intermediate context layer step to work with this?
I will test adding this. Must also be performant in terms of speed and reliability.
> Do you need to provide working examples for the tool to know how joins and relations are usually handled?
Normally AI can infer that from the schema. If not you can "teach" AI using RAG: https://www.sqlai.ai/posts/enhancing-ai-accuracy-for-sql-gen...