redraiment's comments

On: Build a DuckDB Extension in Rust in 4 Commands

[redraiment]

cargo-duckdb-ext-tools v0.5.0 just released, a Cargo plugin that makes writing DuckDB extensions in Rust feel like a normal Rust workflow.

On: Solving the Character Encoding Issue When Reading DuckDB via ODBC in Excel VBA

[redraiment]

This article explains why Chinese text appears garbled when reading data from DuckDB through ODBC in Excel VBA — and how to fix it.

On: Rusty-Sheet: An Excel/WPS/OpenDocument Spreadsheets File Reader for DuckDB

[redraiment]

Oh, my bad! I forgot to update the documentation: Actually, in union by name mode, all worksheets are now analyzed; otherwise, it remains limited to the first sheet only.

On: Rusty-Sheet: An Excel/WPS/OpenDocument Spreadsheets File Reader for DuckDB

[redraiment]

[rusty-sheet](https://github.com/redraiment/rusty-sheet) is a DuckDB extension written in Rust:

* File Formats: Excel, WPS, OpenDocument. * Remote Access: HTTP(S), S3, GCS, Hugging Face. * Batch Reading: Multiple files & sheets. * Schema Merging: By name or by position. * Type Inference: Automatic + manual override. * Excel Range: `range=’C3:E10'` syntax. * Provenance: File & sheet tracking. * Performance: Optimized Rust core.

On: EDBC is Emacs-Lisp-based data access technology

[redraiment]

You are right! Hence, during the process in edbc.el, it would wrap the string with quote('), and replace every quote in the string to two quotes('', not double quotes).

[andrewcooke → redraiment]

no, you're misunderstanding me (i think?). what you describe escapes strings - it sounds correct, but it is not what i am asking about.

for example, when using postgres you might want (for some crazy reason) to have a table called "select". you can do that with:

select * from "select";

where the "select" is not a string, but a quoted name. without the quotes it would be a syntax error (as select is a reserved word). how would that work in edbc?

[redraiment → andrewcooke]

Oh, I got it... It will be problem currently. I'll put it in TODO list. Thanks! ^_^

On: EDBC is Emacs-Lisp-based data access technology

[redraiment]

Actually, EFBC is from another project, Emacs-cgi, which use to create CGI script. Hence, it's run on server only. At first, it's only works with Sqlite, and Add MySQL support yesterday, so I created a new project for it.

[S4M → redraiment]

Oh I see, so you can use emacs to build server apps. That's clever, but then again, is there a special advantage in running the app from emacs?

[JoelMcCracken → S4M]

Side note, but elnode: https://github.com/nicferrier/elnode

which is used to power http://www.teamchat.net/

I think the move to program "real" applications in Emacs is smart. It encourages improvements in Emacs Lisp itself, and it leverages the skills we already have in programming Emacs.

[redraiment → S4M]

For me, there are some reasons: * I like use org-mode to write my Blog, it's very cool if there is a Blog system powered by Emacs-Lisp. * For now, use PHP, JSP or any other tech to build web app, you need works with HTML, CSS, PHP... However, in Lisp, everything can describe in List (like SQL in EDBC). You can refer https://github.com/redraiment/emacs-cgi to see embedded HTML in elisp. * There are many function for text edit in Emacs ready. Hence, I think it will suitable for build server apps.

On: EDBC is Emacs-Lisp-based data access technology

[redraiment]

Yep! Actually, the name "EDBC" is from "JDBC" as well.

On: Using Emacs Lisp for CGI scripting

[redraiment]

News: it can access database by edbc (Emacs Database Connectivity) mode. Presently, it only support Sqlite.

On: Using Emacs Lisp for CGI scripting

[redraiment]

Precently, it provides: 1. Generate HTML from sexp. 2. Nested scriptlets <% %> and <%= %>. 3. Process GET/POST request parameters. 4. Access cookie. 5. Access session. 6. URL redirect. 7. Page forward.

On: Using Emacs Lisp for CGI scripting

[redraiment]

Do you means emacs mode for this stuff? If so, I think the emacs-lisp-mode is enough.