Hi, I will not have time to implement this feature, but if you want to try, please go ahead. Patches are welcome.
> You wrote that it's stored in the *user* home directory and the file is > readable by the owner only and that's IMHO about all what can be done for > security (encryption by a key stored in a program is pointless and entering > the key is too much hassle for such a feature). > I mean, a remote client can see queries that were executed by a different remote client. That might be a problem. Encrypting the queries isn't needed I think. But I can see that it could be a problem for someone, so I'd make it > optional. > If you want to implement this feature, yes please make it optional (disabled by default). That's a bit counter-productive, as I'm doing the same things both locally > and on the server, so I can use the same history for both. > OK let's not split the history for now. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
