Lars Fosdal

Apple's RAM and disk prices are ridiculous, but personally I'd go for at least 24GB and 1TB. My MBP M1 has 32GB/2TB.

Looks fixed now.

I have the weirdest issue. I just installed a fresh Delphi 11.1 + patches on a new, fully patched Windows 10 Enterprise laptop. For some weird reason - I can't debug. Breakpoints don't break. Exceptions break shows assembly code, says it is mixed mode, but no source lines show, and I can't trace to next sourceline. Yes, I am in 32-bit debug mode. Yes, the project has the debug settings and debug info included. Yes, the output folders have full access for the current user. Yes, there is only one set of DCUs in the path. Yes, there is only one .EXE file. Edit: Yes, they are debug DCUs Yes, line endings are CRLF Yes, current user has local admin rights As soon as my app starts, the breakpoints are grayed out. Edit 2: It does not happen to all apps. The problem app is about 600k lines. Tiny apps and a larger 1100k line app - no problems. What am I missing? Update - Possible causes? A developer on a non-corporate laptop does not have this problem. Another developer on corporate laptops have the same problem as me on both new and old laptops. That seems to indicate a Windows policy may be a factor here. Anyways - workaround: Project | Options | Linking | Include remote debug symbols: A tick here gave working breakpoints for us.

IMO, if you need multiple values for a field, you should use a list element. Duplicate key/value pairs in JSON just doesn't make sense. https://JsonLint.com does not like them either.

Sorry, no updates. Not using Delphi much, except from small utils. Haven't checked on the problem since 12.3.

AFAIK, no. You could run it through an RSS reader. Perhaps there is one that can ignore topics the way you desire?

@ŁukaszDe You find a topic uninteresting, but it keeps reappearing? Have you tried the "Ignore this topic" for a thread you don't want to read again?

Yeah, THAT surfaced the dreaded error [dcc64 Error] NonNullableConstraint.dpr(41): Type parameter 'T' must be a non-nullable value type Half-baked patches are no fun. Edit - Also noticed that the Error ID is lost when using MSBuild.

@Anders Melander I just tried my example code which failed before the April patch in the 64-bit IDE, targeting 64-bit Windows. It no longer stops compiling. program NonNullableConstraint; {$APPTYPE CONSOLE} {$R *.res} uses System.SysUtils; type TMyClass = class function Select<T:Record>(const selector: string):TArray<T>; end; TNotifcationRow = record const Query = 'SELECT * FROM v_server_notifications'; public Id: Integer; Name: String; Data: String; ByWho: String; CreatedWhen: TDateTime; function DataAsId: Integer; end; TServerNotificationArray = TArray<TNotifcationRow>; { TMyClass } function TMyClass.Select<T>(const selector: string): TArray<T>; begin end; procedure Test; var MyClass: TMyClass; Res: TServerNotificationArray; begin MyClass := TMyClass.Create; Res := MyClass.Select<TNotifcationRow>('foo'); // <- E2512 Type parameter 'T' must be a non-nullable value type end; { TNotifcationRow } function TNotifcationRow.DataAsId: Integer; begin Result := 0; end; begin try Test; except on E: Exception do Writeln(E.ClassName, ': ', E.Message); end; end.

It is fixed. It is no longer necessary to remove the record constraint to avoid the non-nullable type error. Edit: Woops - missed that 64-bit thing... do you mean the 64-bit target, or the 64-bit compiler?

You can reserve a video against embedding, so that might be a factor?

Correct me if I'm wrong - but isn't the Delphi String automatically converted to/from UTF-8 (or other native db string formats) by FireDAC / Driver?

Why convert when you can enjoy the verbosity and indentation in all its glory? https://www.rocketsoftware.com/en-us/products/cobol/visual-cobol 🙂

I use PowerShell + dbatools module to do backups and restores, as well as check for space, database schema sync, check contents of DB and run scripts, etc.

Due to the continued abuse, the following functionality will change from this date: Images, links and emojis are generally disabled Text emojis will be allowed Quoting limitations will be enforced to single sentences AI filters will be applied to the posts to moderate strong language, personal attacks, and spam Lack of proper grammar, punctuation and Capitalization will be penalized Humorous comments must achieve a rating of at least 42 to be accepted as humor Cat images will be allowed on Saturdays(no nudes, i.e. cats without hair) Recursive posts will be moved to Posts, Recursive Cursive fonts will be righted Use of blinking fonts for important spam is encouraged Links to Rick Astley music videos are encouraged

Considering every major ERP vendor is moving to cloud, I would say that the trend is "no". However, these are typically enterprise sized ERP systems. There may be a niche for small shop owner ERPs - but there are already tons of these out there, and even some of those are cloud based. As soon as you exceed a single user, you are in database territory, and when you talk mobile apps, you definitively are in web service country. I would suggest that you really research your intended target audience to see if there is a gap where a desktop app could fill a need. I would also suggest that you narrow down and "modularize" your functionality, because the concepts of ERP systems and their near relatives are REALLY far reaching. You may suddenly find yourself in Tax, CRM, HR & Salary, document management, EDI and WMS territory.

https://www.theregister.com/2025/02/13/hash_table_breakthrough/ adds some further detail on a different paper, "Optimal Bounds for Open Addressing Without Reordering" which is related to the first "Tiny Pointers" paper. And these Python implementations derive from that paper: https://github.com/sternma/optopenhash

Yeah, that was my thoughts as well. Still, it is fascinating to see innovative ideas on old subjects.

And... now in the correct thread... Did you guys read the article on the undergraduate that suggested new improvements to hash tables? Article: https://www.quantamagazine.org/undergraduate-upends-a-40-year-old-data-science-conjecture-20250210/ "Tiny Pointers" Paper: https://arxiv.org/abs/2111.12800

Indeed. The change to 12.3 is really complicating existing code, and although I am not against breaking changes for improving quality, it means that you can't really use 12.3 without rewriting parts of the code. Since we never did go for 12.0 ,12.1 or 12.2, I suspect our projects will stay on 11.3, since the product has entered the care and maintenance phase.

That is technically correct but simply changing from string to string[n] in a record as a workaround to the non-nullable type Generics issue, will cause these warnings.

@bravesofts Place a feature request at EMBT's JIRA. Nothing is decided on this board.

Same for me. Several record types where I had to explicitly add a string length, resulting in numerous [dcc32 Warning]: W1057 Implicit string cast from 'ShortString' to 'string'

I agree. Bold-overuse is as bad as shouting in CAPS. It doesn't improve the delivery of the messages, nor the quality of the arguments.

Leading question - so.... what would you check next, Mike?