![]() Looking at the updated help page - section Writing and executing SQL statements / Controlling the schema search path for PostgreSQL and Redshift found here. So the workaround for that is creating a new console window everytime I want to run a report and only being able to export once before, I have to move to another window if I made any changes to my query. Then I noticed something - When it runs the query the first time, the tool picks a default schema (upper right-hand corner of the console window) and once it has picked the default schema it stays that way when I re-open the file or DG. I am querying against a Redshift data source and when I first open and run a SQL query it lets me export the results but stops working upon re-opening or restarting DG. ![]() Copying such data to the Clipboard should be trivial.I already submitted a ticket, but I think I was able to figure out my issue. Therefore you can display data from several different sources ON THE SAME FORM, merely by pointing the TDataSource at a different database, and, maybe, changing the TDataSet.Īs to the question proper, is there a good reason why Gizmo can't/shouldn't use one of the CSV DataSets available in Lazarus? This, after all, would store the data in a CSV file directly, can display it in a DBGrid, or even, a StringGrid. The TDataSet component you drop on a Form is an access tool for this database, normally a TDataSource, which provides mechanisms for the TDataSet to read and write data to the database. The data is stored in the underlying database, whatever form it takes. NONE of the GUI tools store data in any way, shape or form, unless you specifically design them to do so. This question demonstrates perfectly a misunderstanding common to database novices - the confusion between the "data", held in the database, and the GUI tool displaying that data. Quote from: Gizmo on September 20, 2017, 05:06:55 pm OK, so my journey into using SQLIte is gaining momentum, but problems are starting to appear. That TBufDataset is fast but it is memory based, so it is likely to cause problems for large data volumes. But it doesn't seem to have the output flexibility that StringGrids have. I need a robust solution that can store large volumes of data, and SQLIte with DBGrid seems to be the answer. There are a few hacks and other solutions that I have Googled involving creation of stringlists and memos and various other things, but they all seem rather convoluted as well.Ĭan I just check before I go any further that there is not an easy way to save\output the result of DBGrids to files and clipboards? If neither of these are possible, I don't think my adventures into SQLIte will continue. From what I can see, neither seem built into the component. My users have to have the ability to save to at least CSV file (I can manually do HTML) and they need to be able to copy to clipboard. So I'm wondering if I am going wrong somewhere there.Īnyway, that is two issues that I have incorporating SQLIte with DBGrids in Freepascal. ![]() Although there is a "SaveToFile(filename)" procedure in DBGrid, the resulting output is scrambled XML from what I can see. I can't easily save the content of the DBGrid to a CSV file, whereas with StringGrids I could easily save using SG.SaveToCSVFile. I can't easily copy the content of the DBGrid to clipboard, whereas with StringGrids I could easily save using SG.CopyToClipboard OK, so my journey into using SQLIte is gaining momentum, but problems are starting to appear.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |