You can store the intermediate calculation data in temporary tables. This feature solves the issue of temporarily storing the intermediate results of an application, which frees you from frequently creating and dropping tables. I'd like to catch that error and pop open a "try again in 5 minutes" message but I am not sure how to catch an error using the aws api.The temporary tables feature is introduced in TiDB v5.3.0. My ci3 app can't find the bucket to bring down the images about 10% of the time and I get a 500 error. So when a user logs in I download their images to the server. I use koolreport and was not able to get kr to directly use images on s3. Here are some important points for others. I managed to get the temporary tables working. About 10% of the time the bucket is not found and I get a 500 server error. The lack of tools makes this trial and error.Īs of now it is working fine. Errors in sql on creation of temp tables don't display.ģ. There is no way to see what temp tables exist.Ģ. Here are some important points for others.ġ. What do I do about this? If I write the prefix into a cookie, the next time _construct() runs, it will overwrite the cookie.īTW, are you using temp tables on SQL Server? In you opinion, will CI3 sql code that works on mysql also work on sqlserver, without changes? I have been playing with the idea of moving the report generation code to a stored procedure for a FEW YEARS. But is seems that "_construct()" is running numerous times, overwriting my 'prefix'. My plan is to use the prefix+table name to DROP the garbage tables when the user logs out. BUT, I am creating the 'prefix' in the _construct() of my controller and saving the prefix in a $_SESSION variable. When the user wants to exit the app, I drop all the tables that start with that user's id+timestamp. I had to name each with the user's id plus a timestamp. I switched all my temp tables to regular tables. The rds pricing on it seems cheaper than mysql. You can call stored procedures in SQL Server by using an SQL query. (09-30-2022, 01:16 AM)>JustJohnQ Wrote: Yes, CI3 works with MS SQL Server, I am actually using it in one of my projects. What can I look at to determine if I am still in the original session? And a user can run a subreport, directly from the first report. I actually have mine split into a two functions in a model. So, what makes a different session? a different function? How can I check this? BUT table_exists still didn't show the table existing! I tested it in mysqlWorkBench and fixed it (the sql error). I finally realized that my creation of the temp table wasn't working due to some SQL errors. With jmeter I needed to delay starting reports for 5 or 6 seconds each. It worked very smoothly until I started load testing with Jmeter. They can then print it and then chose another year without my code recalculating. Then a user can chose which year they want a report for. What I do is build the temp tables for 10 years at the same time. If I knew table_exists didn't work for temp tables that would have saved me lots of angst! I also figured that the speed of operations would be increased by using tables in RAM, like the old RAM drives we used to use way back. That is the reason I am building the temp files. The report is pretty big and consists of all kinds of data sliced and diced. THANK YOU! I use Koolrepport to generate a report. Table_exists() doesn't work for temporary tables, the result is always false.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |