Pike-devel May 2012

pike-devel@lists.lysator.liu.se

7 participants
7 discussions

Sql.pgsql behavior in case of errors
by aldem-pikedev＠aldem.net 21 Aug '14

21 Aug '14

Hi everyone, I am preparing to use Postgres in my app, found the following strange behavior: ---snip--- Sql.Sql db = Sql.Sql("pgsql://localhost", "test", "test", "test"); db->query("BEGIN"); db->query("INSERT INTO requests (SvTrId) VALUES ('lala')"); catch(db->query("INSERT INTO requests (SvTrId) VALUES ('lala')")); db->query("INSERT INTO requests (SvTrId) VALUES ('juju')"); db->query("ROLLBACK"); ---snip--- Database is opened, row with 'lala' is inserted, second query (obviously) fails as SvTrId is the primary key, but row with 'juju' is inserted *and* appears in the database - i.e. the transaction is *committed*! Studying source code show, that once error is encounter, session is reset, i.e. running transaction is rolled back, everything is closed, temporary tables are deleted and session variables are reset as well, and after that, the next statement(s) will be committed immediately, as there is no active transaction. In my opinion, this is not exactly correct behavior when statement fails, as session still may be needed (especially temporary tables, open cursors etc). Im some cases, this is perfectly normal when SQL statement fails, especially in SERIALIZED transaction isolation level, and it would be more practical to leave the decision as of what to do to the application. Yes, this is true that it is impossible to continue executing statements in failed transaction, but temporary tables etc. may still be needed. Also, silent reconnection is not a good idea too - when there are many transactional statements are executed - it would be nice to have an option to modify this behavior. Best regards, /Alexander

5 6

Pike 7.8 Release (last call)
by H. William Welliver III 13 Jun '12

13 Jun '12

Does anyone have any objections to 7.8.680 becoming the next official release of Pike? Do note that machine code is non-functional on (at least more modern instances of) i386. If I don't hear any objections in 24 hours, I will attempt to update the website, etc, with the new information. Best, Bill

9 18

libusb and autoconf
by Stephen R. van den Berg 03 Jun '12

03 Jun '12

Just in case someone happens to be working on it, I'm in the process of implementing a native interface to libusb-1.0 from within Pike. The sad part is that actually programming the interface is not that much work, generating proper configure.in files *is* however a big PITA. Has anyone ever considered using cmake or jam instead of autoconf ? I'm not saying I know it to be better, but it just seems like it can't get any worse either (besides simplicity, it definitely could be faster, the current configure business is a resource hog, timewise). -- Stephen. "Always remember that you are unique. Just like everyone else."

3 10

strict type regression
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 16 May '12

16 May '12

I've started getting /home/nilsson/pike/lib/modules/String.pmod/module.pmod:98: Warning: An expression of type string | int | !mixed cannot be assigned to a variable of type int. after the changes in there. It should be possible to work out that int sz = min(@map(strs, sizeof)); is always the correct type.

2 2

pike_frame->fun = FUNCTION_BUILTIN
by Arne Goedeke 14 May '12

14 May '12

In INIT, EXIT and some gc callbacks the fun in Pike_fp is set to FUNCTION_BUILTIN. there are some places in the code (e.g. ADT.List()->_get_iterator) where ->fun is used in INHERIT_FROM_INT et al, which segfaults (except with PIKE_DEBUG). I am not sure where to fix this. Should the *_FROM_INT macros check for FUNCTION_BUILTIN or is this better to be handled in the individual INIT/EXIT methods ? does anyone object to making ADT.Stack and ADT.Queue inherit ADT.List? arne

2 1

Pike 7.8 Beta
by H. William Welliver III 13 May '12

13 May '12

I've prepared a new 7.8 test release for consideration. Please feel free to download and test. http://pike.ida.liu.se/download/pub/pike/beta/7.8.680/ I am not aware of any show stoppers in this release; if none are found in the next week, this will become the new stable 7.8 release. As always, please feel free to get in touch with any comments or concerns. Best, Bill bill(a)welliver.org

6 16

Visualization of inherit-graphs
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 11 May '12

11 May '12

6 13

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel May 2012